Purchase Order SAP abap statement

Hi ABAP Expert,
Need your help to solve my issue;
If i what to get the detail on the PO number , i can get from table EKPO
get EKPO-EBELN from EKPO
how do i use sap statement to get the detail below
1. PO with GR and Invoice
2. PO with GR without Invoice
3. PO without GR and Invoice

You can get these from the table EKBE with the field BEWTP
Check the table EKBE.
1. PO with GR and Invoice
2. PO with GR without Invoice
3. PO without GR and Invoice
Regards
Gopi

Similar Messages

  • Conversion of Purchase Order sap withgoods reciept done

    Hi
    In legacy system the Purchase order and goods receipt done ,now the invoice is to be done in  SAP. Can you please advice how the invoice can be posted in SAP,with reference to purchase order or create an invoice in FI. Please advice.
    Regards
    Rekha

    Normally, after a FI Invoice document is generated in the system, FI makes the payment through Payment Run separately. But in your case, if you need to create a invoice first then cost has to be assigned to some CO object or any other accounts. So would suggest to for FV60 - Park Incoming Invoices and distribute the cost to G/L accounts. Then based on this payments can be processed.
    /Manoj

  • Account Asssignment in the Purchase order SAP ECC 6.0

    Hi
    I am trying to create Purchase order with Account assignment category "Q"  wherein system displays a GL account (4011100) which is mapped in the OBYC in the transaction GBB and general modification VBR. Further when I enter WBS element, it changes  GL account to  2301100 which is mapped in the transaction BSX. You are requested to kindly let me know what is logic behind GL account change, Is there any setting of WBS element with transaction BSX ?
    Can I change vendor code in the purchase order mofification ME22N before PO release.
    regards
    Sanjay

    Hi,
    For Projects the PRs and POs are the commitements.
    So while creating the PRs and POs the system always looks at the balance sheet account which is mapped in BSX.
    During the actual posting/ Goods issue to project the system will credit this balance sheet account and debit the P/L account from VBR.
    So syetm bahaviour is very much correct.
    Hope its clear,
    Reward point if useful.
    Thanks..

  • Reject Purchase order using abap OO class CL_PO_HEADER_HANDLE_MM

    Hi all,
    We have created a webdynpro application for maintaining purchase
    order by using class CL_PO_HEADER_HANDLE_MM.
    With this class we are able to release (method RELEASESTATE_MM~RELEASE)  or cancel release..
    We are trying, in vain,  to reject purchase order by using method IF_RELEASABLE_MM~REJECT
    even if sy-subrc eq 0 .
    any idea ?
    thanks.

    Hello
    Have you had a look whether you can reject the PO at all using method
    IF_RELEASABLE_MM~IS_REJECTION_ALLOWED
    Regards
       Uwe

  • Purchase order SAP

    How can we see the Vendor description  while creating Purchase Order .Usually when we create PO and do the backspace it just show the Vendor number not description.Is there  a way we can see description also.

    Hi,
    During PO creation in vendor input data option we will give vendor code or if vendor code is not know and then we will select vendor search option ( click vendor code input data option down arrow) & to be provide india. The vendor description is available with india all vendor displayed and selected PO creation vendor. Now, vendor code with description displayed.
    Then, next PO going to be create in vendor input data option you will press backspace key it will shown previously  all PO created vendor codes. At present If know PO creation vendor code to be select or follow the above vendor search option.  Here, vendor code only input data  and then enter key press  the vendor code with description displayed.
    So, if PO created vendor code only shown in this vendor input screen.
    Now, your are understand the vendor input data concept. 
    Regards,
    K.Rajendran

  • ME23N - Read Last Purchase Order for Display

    Hi,
    We are upgrading from 4.6C to ECC6 and one of the problems the users have identified is that when displaying the purchase order with transactions ME22N or ME23N the last purchase order that was worked on is not always the one that is displayed.
    This is very evident when creating a PO with ME21N and then switching to view it on ME23N - in ECC6 the PO that was created is never the PO that is displayed on ME23N; whereas in 4.6C creating a PO with ME21N and switching to ME23N the PO that was created is ALWAYS the PO that is displayed on ME23N.
    It this feature (whatever) no longer available with ECC6?  Is it a configuration settings that we haven't properly set in ECC6? 
    Thanks for any help.
    Martha

    I analysed how SAP remembers the previous purchase order number in transaction ME23N in version 4.7 as I do not have access to version ECC6. In version 4.7 transaction ME23N reads table ESDUS (MM: Dynamic User Settings) in the following way
    ESDUS-UNAME = sy-uname
    ESDUS-ACTION = 'MEPO'
    ESDUS-ELEMENT = 'Application         Po_Process'
    The purchase order number is the first 10 characters of ESDUS-ACTIVE (ESDUS-ACTIVE+0(10)).
    When you read a new purchase order SAP writes that order number to table ESDUS using function module ES_SAVE_USER_SETTINGS. When you revisit the transaction SAP uses function module ES_READ_USER_SETTINGS to read the purchase order number stored in table ESDUS.
    Ask an ABAP programmer to investigate this in your system with the information I have provided you. He/She should be able to find out what is going wrong. I am limited because I do not have access to your system. Hope this helps. Please let me know what the ABAP programmer found out.

  • Authority mail while releasing purchase order

    Hello Experts,
    My requirement is when the person release the purchase order(SAP-MM) of certain amount then email will trigger to the  authorized person and once he approves then only PO will get released.
    Is there any work of ABAP in this, If yes, How this functionality can be achieved through abap and what are the user exits I need to apply.
    Please help.

    Yes It is possible. You have to write an enhancement in Program LMEGUICJI after get PO has been saved (committed) .
    her you will get all the info about the PO after being Commit Work executed After ->POST.
    You will also get the release strategy information using the FM "BAPI_PO_GETRELINFO ". Based on The release strategy and amount in PO you can send mail using the FM "SO_NEW_DOCUMENT_ATT_SEND_API1".
    Hope this will solve your purpose.

  • Lock Purchase Order fields after goods receipt

    Hello everyone,
      I need to be able to set a couple of fields in ME22N as display only after goods receipt has been done for the PO. Is there any config that I can do to get this done? Any idea or suggestion?
      Thank you very much for your help!
    Kelly.

    You can change PO after GR in standard SAP and there is no standard customization feature available to block that.
    Use ABAP to check for GR against the PO and block PO fields once GR is posted.
    Use tables MKPF for GR posting, EKKO and EKPO for Purchase Order.
    ABAP will have to change the field status of Purcahse Order screens as blocked, if GR is posted.
    It might be added as a subroutine that gets triggered after each GR posting.

  • Shipment cost documents in automatic purchase order

    Does somebody can help me about a shipping problem ?
    While transferring shipment cost documents to FI-co with automatic generation of purchase order, SAP create one purchase item order for all my shipment cost documents. Is it possible to customize the purchase order to get 1 item  purchase order by shipment cost documents ?
    In my case, i have 1 purchase order with only one item that contains several entry sheet..
    CMA

    Hi AP,
    Thanks for your reply. When you said "it will be possible to create multiple service entry with reference to the same purchase order."
    I'm agree with you but all the services entry with reference to the same purchase order are grouped on the same item post.
    In my purchase order I would like to have one item by services entry.
    I expect to to have 1 purchase order with several item ( one for each shipping)
    1 services entry = shipment cost document =  1 Shipping.
    Is it possible to do that with SAP in standard ?
    It exists a lot of oss notes on this topic but they don't solved my problem, and sap documentation is not clear on this topic.
    CMA

  • ADDITIONS OF CONDITIONS IN RETURN PURCHASE ORDER

    CAN YOU PLEASE TELL HOW CAN I ADD CONDITIONS IN RETURN PURCHASE ORDER THROUGH ABAP

    I HAVE CREATED A RETURN PO THROGH BAPI_PO_CREATE BUT IT IS NOT TAKING ANY CONIDTIONS AND WHEN I AM TRYING TO INSERT CONDITIONS THROUGHT BAPI_PO_CHANGE IT IS NOT TAKING THOSE CONDITIONS

  • How can I send purchase order through SAP mail ?

    How can I send purchase order through SAP mail ? Can any one explain whts the NACE settings?

    just  do it as  <b>Anji reddy</b> said to you   ...or else  ...  in the purchase  order trascation  ...print it  ... so that  it will generate the spool request  for that  purchase  order  ....
    so the   the belwo program is for sending <b>the Spool   Request  data   as  Email  to  any Email id  ...</b>
    The code below demonstrates how to retrieve a spool request and email it as a PDF document. Please note for the below program to process a spool request the program must be executed in background otherwise no spool request will be created. Once you have had a look at this there is an modified version of the program which works in both background and foreground. Also see transaction SCOT for SAPConnect administration.
    *& Report  ZSPOOLTOPDF                                                 *
    *& Converts spool request into PDF document and emails it to           *
    *& recipicant.                                                         *
    *& Execution                                                           *
    *& This program must be run as a background job in-order for the write *
    *& commands to create a Spool request rather than be displayed on      *
    *& screen                                                              *
    REPORT  zspooltopdf.
    PARAMETER: p_email1 LIKE somlreci1-receiver
                                        DEFAULT '[email protected]',
               p_sender LIKE somlreci1-receiver
                                        DEFAULT '[email protected]',
               p_delspl  AS CHECKBOX.
    *DATA DECLARATION
    DATA: gd_recsize TYPE i.
    * Spool IDs
    TYPES: BEGIN OF t_tbtcp.
            INCLUDE STRUCTURE tbtcp.
    TYPES: END OF t_tbtcp.
    DATA: it_tbtcp TYPE STANDARD TABLE OF t_tbtcp INITIAL SIZE 0,
          wa_tbtcp TYPE t_tbtcp.
    * Job Runtime Parameters
    DATA: gd_eventid LIKE tbtcm-eventid,
          gd_eventparm LIKE tbtcm-eventparm,
          gd_external_program_active LIKE tbtcm-xpgactive,
          gd_jobcount LIKE tbtcm-jobcount,
          gd_jobname LIKE tbtcm-jobname,
          gd_stepcount LIKE tbtcm-stepcount,
          gd_error    TYPE sy-subrc,
          gd_reciever TYPE sy-subrc.
    DATA:  w_recsize TYPE i.
    DATA: gd_subject   LIKE sodocchgi1-obj_descr,
          it_mess_bod LIKE solisti1 OCCURS 0 WITH HEADER LINE,
          it_mess_att LIKE solisti1 OCCURS 0 WITH HEADER LINE,
          gd_sender_type     LIKE soextreci1-adr_typ,
          gd_attachment_desc TYPE so_obj_nam,
          gd_attachment_name TYPE so_obj_des.
    * Spool to PDF conversions
    DATA: gd_spool_nr LIKE tsp01-rqident,
          gd_destination LIKE rlgrap-filename,
          gd_bytecount LIKE tst01-dsize,
          gd_buffer TYPE string.
    * Binary store for PDF
    DATA: BEGIN OF it_pdf_output OCCURS 0.
            INCLUDE STRUCTURE tline.
    DATA: END OF it_pdf_output.
    CONSTANTS: c_dev LIKE  sy-sysid VALUE 'DEV',
               c_no(1)     TYPE c   VALUE ' ',
               c_device(4) TYPE c   VALUE 'LOCL'.
    *START-OF-SELECTION.
    START-OF-SELECTION.
    * Write statement to represent report output. Spool request is created
    * if write statement is executed in background. This could also be an
    * ALV grid which would be converted to PDF without any extra effort
      WRITE 'Hello World'.
      new-page.
      commit work.
      new-page print off.
      IF sy-batch EQ 'X'.
        PERFORM get_job_details.
        PERFORM obtain_spool_id.
    *** Alternative way could be to submit another program and store spool
    *** id into memory, will be stored in sy-spono.
    *submit ZSPOOLTOPDF2
    *        to sap-spool
    *        spool parameters   %_print
    *        archive parameters %_print
    *        without spool dynpro
    *        and return.
    * Get spool id from program called above
    *  IMPORT w_spool_nr FROM MEMORY ID 'SPOOLTOPDF'.
        PERFORM convert_spool_to_pdf.
        PERFORM process_email.
        if p_delspl EQ 'X'.
          PERFORM delete_spool.
        endif.
        IF sy-sysid = c_dev.
          wait up to 5 seconds.
          SUBMIT rsconn01 WITH mode   = 'INT'
                          WITH output = 'X'
                          AND RETURN.
        ENDIF.
      ELSE.
        SKIP.
        WRITE:/ 'Program must be executed in background in-order for spool',
                'request to be created.'.
      ENDIF.
    *       FORM obtain_spool_id                                          *
    FORM obtain_spool_id.
      CHECK NOT ( gd_jobname IS INITIAL ).
      CHECK NOT ( gd_jobcount IS INITIAL ).
      SELECT * FROM  tbtcp
                     INTO TABLE it_tbtcp
                     WHERE      jobname     = gd_jobname
                     AND        jobcount    = gd_jobcount
                     AND        stepcount   = gd_stepcount
                     AND        listident   <> '0000000000'
                     ORDER BY   jobname
                                jobcount
                                stepcount.
      READ TABLE it_tbtcp INTO wa_tbtcp INDEX 1.
      IF sy-subrc = 0.
        message s004(zdd) with gd_spool_nr.
        gd_spool_nr = wa_tbtcp-listident.
        MESSAGE s004(zdd) WITH gd_spool_nr.
      ELSE.
        MESSAGE s005(zdd).
      ENDIF.
    ENDFORM.
    *       FORM get_job_details                                          *
    FORM get_job_details.
    * Get current job details
      CALL FUNCTION 'GET_JOB_RUNTIME_INFO'
           IMPORTING
                eventid                 = gd_eventid
                eventparm               = gd_eventparm
                external_program_active = gd_external_program_active
                jobcount                = gd_jobcount
                jobname                 = gd_jobname
                stepcount               = gd_stepcount
           EXCEPTIONS
                no_runtime_info         = 1
                OTHERS                  = 2.
    ENDFORM.
    *       FORM convert_spool_to_pdf                                     *
    FORM convert_spool_to_pdf.
      CALL FUNCTION 'CONVERT_ABAPSPOOLJOB_2_PDF'
           EXPORTING
                src_spoolid              = gd_spool_nr
                no_dialog                = c_no
                dst_device               = c_device
           IMPORTING
                pdf_bytecount            = gd_bytecount
           TABLES
                pdf                      = it_pdf_output
           EXCEPTIONS
                err_no_abap_spooljob     = 1
                err_no_spooljob          = 2
                err_no_permission        = 3
                err_conv_not_possible    = 4
                err_bad_destdevice       = 5
                user_cancelled           = 6
                err_spoolerror           = 7
                err_temseerror           = 8
                err_btcjob_open_failed   = 9
                err_btcjob_submit_failed = 10
                err_btcjob_close_failed  = 11
                OTHERS                   = 12.
      CHECK sy-subrc = 0.
    * Transfer the 132-long strings to 255-long strings
      LOOP AT it_pdf_output.
        TRANSLATE it_pdf_output USING ' ~'.
        CONCATENATE gd_buffer it_pdf_output INTO gd_buffer.
      ENDLOOP.
      TRANSLATE gd_buffer USING '~ '.
      DO.
        it_mess_att = gd_buffer.
        APPEND it_mess_att.
        SHIFT gd_buffer LEFT BY 255 PLACES.
        IF gd_buffer IS INITIAL.
          EXIT.
        ENDIF.
      ENDDO.
    ENDFORM.
    *       FORM process_email                                            *
    FORM process_email.
      DESCRIBE TABLE it_mess_att LINES gd_recsize.
      CHECK gd_recsize > 0.
      PERFORM send_email USING p_email1.
    *  perform send_email using p_email2.
    ENDFORM.
    *       FORM send_email                                               *
    *  -->  p_email                                                       *
    FORM send_email USING p_email.
      CHECK NOT ( p_email IS INITIAL ).
      REFRESH it_mess_bod.
    * Default subject matter
      gd_subject         = 'Subject'.
      gd_attachment_desc = 'Attachname'.
    *  CONCATENATE 'attach_name' ' ' INTO gd_attachment_name.
      it_mess_bod        = 'Message Body text, line 1'.
      APPEND it_mess_bod.
      it_mess_bod        = 'Message Body text, line 2...'.
      APPEND it_mess_bod.
    * If no sender specified - default blank
      IF p_sender EQ space.
        gd_sender_type  = space.
      ELSE.
        gd_sender_type  = 'INT'.
      ENDIF.
    * Send file by email as .xls speadsheet
      PERFORM send_file_as_email_attachment
                                   tables it_mess_bod
                                          it_mess_att
                                    using p_email
                                          'Example .xls documnet attachment'
                                          'PDF'
                                          gd_attachment_name
                                          gd_attachment_desc
                                          p_sender
                                          gd_sender_type
                                 changing gd_error
                                          gd_reciever.
    ENDFORM.
    *       FORM delete_spool                                             *
    FORM delete_spool.
      DATA: ld_spool_nr TYPE tsp01_sp0r-rqid_char.
      ld_spool_nr = gd_spool_nr.
      CHECK p_delspl <> c_no.
      CALL FUNCTION 'RSPO_R_RDELETE_SPOOLREQ'
           EXPORTING
                spoolid = ld_spool_nr.
    ENDFORM.
    *&      Form  SEND_FILE_AS_EMAIL_ATTACHMENT
    *       Send email
    FORM send_file_as_email_attachment tables it_message
                                              it_attach
                                        using p_email
                                              p_mtitle
                                              p_format
                                              p_filename
                                              p_attdescription
                                              p_sender_address
                                              p_sender_addres_type
                                     changing p_error
                                              p_reciever.
      DATA: ld_error    TYPE sy-subrc,
            ld_reciever TYPE sy-subrc,
            ld_mtitle LIKE sodocchgi1-obj_descr,
            ld_email LIKE  somlreci1-receiver,
            ld_format TYPE  so_obj_tp ,
            ld_attdescription TYPE  so_obj_nam ,
            ld_attfilename TYPE  so_obj_des ,
            ld_sender_address LIKE  soextreci1-receiver,
            ld_sender_address_type LIKE  soextreci1-adr_typ,
            ld_receiver LIKE  sy-subrc.
    data:   t_packing_list like sopcklsti1 occurs 0 with header line,
            t_contents like solisti1 occurs 0 with header line,
            t_receivers like somlreci1 occurs 0 with header line,
            t_attachment like solisti1 occurs 0 with header line,
            t_object_header like solisti1 occurs 0 with header line,
            w_cnt type i,
            w_sent_all(1) type c,
            w_doc_data like sodocchgi1.
      ld_email   = p_email.
      ld_mtitle = p_mtitle.
      ld_format              = p_format.
      ld_attdescription      = p_attdescription.
      ld_attfilename         = p_filename.
      ld_sender_address      = p_sender_address.
      ld_sender_address_type = p_sender_addres_type.
    * Fill the document data.
      w_doc_data-doc_size = 1.
    * Populate the subject/generic message attributes
      w_doc_data-obj_langu = sy-langu.
      w_doc_data-obj_name  = 'SAPRPT'.
      w_doc_data-obj_descr = ld_mtitle .
      w_doc_data-sensitivty = 'F'.
    * Fill the document data and get size of attachment
      CLEAR w_doc_data.
      READ TABLE it_attach INDEX w_cnt.
      w_doc_data-doc_size =
         ( w_cnt - 1 ) * 255 + STRLEN( it_attach ).
      w_doc_data-obj_langu  = sy-langu.
      w_doc_data-obj_name   = 'SAPRPT'.
      w_doc_data-obj_descr  = ld_mtitle.
      w_doc_data-sensitivty = 'F'.
      CLEAR t_attachment.
      REFRESH t_attachment.
      t_attachment[] = it_attach[].
    * Describe the body of the message
      CLEAR t_packing_list.
      REFRESH t_packing_list.
      t_packing_list-transf_bin = space.
      t_packing_list-head_start = 1.
      t_packing_list-head_num = 0.
      t_packing_list-body_start = 1.
      DESCRIBE TABLE it_message LINES t_packing_list-body_num.
      t_packing_list-doc_type = 'RAW'.
      APPEND t_packing_list.
    * Create attachment notification
      t_packing_list-transf_bin = 'X'.
      t_packing_list-head_start = 1.
      t_packing_list-head_num   = 1.
      t_packing_list-body_start = 1.
      DESCRIBE TABLE t_attachment LINES t_packing_list-body_num.
      t_packing_list-doc_type   =  ld_format.
      t_packing_list-obj_descr  =  ld_attdescription.
      t_packing_list-obj_name   =  ld_attfilename.
      t_packing_list-doc_size   =  t_packing_list-body_num * 255.
      APPEND t_packing_list.
    * Add the recipients email address
      CLEAR t_receivers.
      REFRESH t_receivers.
      t_receivers-receiver = ld_email.
      t_receivers-rec_type = 'U'.
      t_receivers-com_type = 'INT'.
      t_receivers-notif_del = 'X'.
      t_receivers-notif_ndel = 'X'.
      APPEND t_receivers.
      CALL FUNCTION 'SO_DOCUMENT_SEND_API1'
           EXPORTING
                document_data              = w_doc_data
                put_in_outbox              = 'X'
                sender_address             = ld_sender_address
                sender_address_type        = ld_sender_address_type
                commit_work                = 'X'
           IMPORTING
                sent_to_all                = w_sent_all
           TABLES
                packing_list               = t_packing_list
                contents_bin               = t_attachment
                contents_txt               = it_message
                receivers                  = t_receivers
           EXCEPTIONS
                too_many_receivers         = 1
                document_not_sent          = 2
                document_type_not_exist    = 3
                operation_no_authorization = 4
                parameter_error            = 5
                x_error                    = 6
                enqueue_error              = 7
                OTHERS                     = 8.
    * Populate zerror return code
      ld_error = sy-subrc.
    * Populate zreceiver return code
      LOOP AT t_receivers.
        ld_receiver = t_receivers-retrn_code.
      ENDLOOP.
    ENDFORM.
    Girish

  • Archiving Purchase Order in SAP 4.6C

    Good day
    My client has upgraded to ECC6 on a new server. They've requested that I archive all the 4.6C data which will then be taken across to ECC6 via the TOA* and ADMI* tables.
    The problem I have now is that there are Purchase Orders that cannot archive due to Received / Invoiced errors, etc. The client is not prepared to correct the transactions and I need a way to bypass the validations in the archiving run to archive the transactions even though they're in error.
    Kind regards
    Mark

    You cannot archive incomplete business processes in general and there might be 30 or more different errors. Resolving all those errors can take months and years. I have several thousand old POs that cannot be closed and archived , because the company was sold and left our SAP system .
    I heard recently  that there is a new functionality in PLM (costs extra money) that allows to archive such records, but I am not certain if it only archives the records but leaves the records in the system or if it deletes the records as well from your system.
    More  confusing to me is your statement: quote}which will then be taken across to ECC6 via the TOA* and ADMI* tables. quote}
    This sounds like you think you could then recreate the POs in ECC6 without needing to migrate them. Can you clarify this.

  • Idocs for purchase order in SAP to SAP

    Hi
    I have to send purchase order from a SAP system to a SAP system, creation and modification both.
    I found these Idocs:
    ORDER in sender SAP
    PORDCR for creation in destination SAP
    PORDCH for update in destinaton SAP
    My problem is that all of three idoc have different segments, so i have to map field by field: is there a different solutions, always using idocs and not BAPI directly?
    Thanks lot.
    Matteo Vernile.

    Hi Matteo,
    To send purchase orders you can use next Idocs:
    1. Creation -->Idoc type: PORDCR102 Message: PORDCR1 This Idoc is based on BAPI_PO_CREATE1
    2 Modification --> Idoc type PORDCH02 Message: PORDCH This Idoc is based on BAPI_PO_CHANGE
    Using standard boldSAP message determinationbold  you can create these Idocs without create any ABAP program.
    If you are not creating the Idoc using the standard Message Determination, you should obtain the data using the bapi BAPI_PO_GETDETAIL.
    Reward points if helps.
    Regards,
    Roger

  • SAP Adapter: Error when committing SAP good receipt on purchase order.

    Hi guys:
    I’m trying to perform a sap good receipt on purchase order, and the BAPIs are the followings:
    1) BAPI_GOODSMVT_CREATE
    2) BAPI_TRANSACTION_COMMIT
    Note: This is only a proof of concept. Therefore, only I'm considering the commit of transaction.
    I’ve followed the example SAPTransaction, but in the moment when the BizTalk is sending the commit (point 2), BT get this error:
    There was a failure executing the send pipeline: "Microsoft.BizTalk.DefaultPipelines.XMLTransmit, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral,
    PublicKeyToken=31bf3856ad364e35" Source: "XML assembler" Send Port: "SP_BAPI" URI: "sap://CLIENT=800;LANG=EN;@a/192.168.0.102/00" Reason: This Assembler cannot retrieve a document specification using this type: "http://Microsoft.LobServices.Sap/2007/03/Rfc/#BAPI_TRANSACTION_COMMIT". 
    The operations:
    <BtsActionMapping xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
      <Operation Name="Bapi" Action="http://Microsoft.LobServices.Sap/2007/03/Bapi/MKPF/CREATEFROMDATA/BAPI_GOODSMVT_CREATE"
    />
      <Operation Name="Commit" Action="http://Microsoft.LobServices.Sap/2007/03/Rfc/BAPI_TRANSACTION_COMMIT"
    />
    </BtsActionMapping>
    Thanks in advance.
    Luis

    Hi Luis,
    Refer to links, they might be useful:
    This Assembler cannot retrieve a document specification
    This Assembler cannot retrieve a document specification
    using this type: "http://www.sap.com/abapxml#abap
    Rachit
    Please mark as answer or vote as helpful if my reply does

  • Planned Order to Purchase Order report in SAP

    Dear All
    The Business process is Planned Order - Converted to Purchase Requsition - Converted to purchase order .
    Is there any report in SAP , which shhows the direct link between Planned order to Purchase Order ?
    Regards
    Shyam

    I have never seen a standard report, build a query based on tables PLAF, EBAN and EKET should be involved

Maybe you are looking for