How to delete the production order in mass?

Dear Experts
             Please tell me how to delete the  old production orders?

Raja,
CO78 is a one stop transaction for production order setting deletion flag, deletion indicator, archiving and finally deleting.
Generally we schedule the following programs in background in the sequence below,
1. PPARCHP1 for Setting Deletion Flag
2. PPARCHP1 for Setting Deletion Indicator (Once set cannot be revoked- so care should be taken in selection of orders)
3. PPARCHA1 for archiving the production order with Deletion Indicator active. Basis should set the database/storage space for archiving/storing the records.
4. PPARCHD1 for Deleting the records from SAP database.
Regards,
Prasobh

Similar Messages

  • How to view the planned orders in mass and how to delete in mass

    Hi gurus,
    How to view the planned orders in mass and how to delete in mass.
    Regards
    R.Rajakarthik

    Hi,
    Use the collective display of planned orders, transaction code MD16.
    You can select the data by different options and choose which ones or all that you need to delete.
    Click the Delete button to trash them.
    This will delete planned orders without deleting the planned independent requirements and sales orders.
    Hope it helps

  • IMP: How to delete the service order

    Hey Experts,
    Can you tell me how to delete the service order which was created in IW31..? or we have any Functions Module to delete the service order?
    and one more question is I have more than 100 service order in the table ,but it will display only 50 order when i execute this Functions Module BAPI_ALM_ORDERHEAD_GET_LIST
    can you tell me how to solve this problem...?
    Thanking you in advance,
    Regards
    J Sarathi

    This is what the BAPI_ALM_ORDERHEAD_GET_LIST documentation says
    "You can use this method to determine a list of orders according to a list of selection criteria. The number of hits that are produced for the person calling up the list, can be specifically reduced; without further parameter transfers, the first 50 hits are displayed. A complete list of the hits is stored internally. If you call up the selection again within a Logical Unit of Work (LUW) without changing the selection parameters, but with other refurbishment parameters, then you receive further partial quantities of the selection result, as specified by you."
    and for deletion
    check whether you can set any deletion status through the fm BAPI_ALM_ORDER_MAINTAIN
    Also check the business objects BUS2007, BUS2088

  • How to delete  Open Production Orders

    Hi,
    I would like to Delete Open Production Orders.plz tell me How to delete  Open Production Orders

    Hi
    for deleting POs you have to delete the line items. First select the line items and then choose the icon 'delete' in the item overview screen of PO.
    For open PO s also you have to do the same Or else change the PO quantity to the desired qty for what GRN has been made.
    Regards
    Siva

  • How to delete the empty orders in v.06 tcode

    Hi,
    i am trying to delete the empty orders in V.06 transaction code, but it is not allowing to delete.
    the same order is able to delete from the VA02 Transaction. so could you please advice me to delete from V.06 transaction.

    Hello Ganesh,
    i am trying to delete the empty orders in V.06 transaction code, but it is
    not allowing to delete.the same order is able to delete from the VA02
    Transaction. so could you please advice me to delete from V.06 transaction.
    Please note that the T-code (V.06) which you have been using basically shows up all Incomplete Documents like Sales Order, Contracts, Inquiry. Pertaining to each document you will be able to see all the missing fields which are actually set as part of Incompletion Log.
    There is no dirrect provision to delete Sales Document using this t-code without opening up the document in change mode...If incase you plan is to delete the Sales Document which are not complete, then use this T-code to extract all the Sales Document and then use MASS t-code to delete...
    As per best SAP practice, deleting of Sales Document is not recommended at all, instead you can use REJECTION OPTION...  
    Regards,
    Sarthak

  • How to check the Production order exits

    Hi Experts
    Modification to processing of Command Orders & Tickets
    We require a modification to the processing being performed on sales data originating from the Command Concrete system and potentially from other systems yet to come online (e.g. Pinkenba Cement plant).
    The Sap process involved is ZINT_INBOUND_POLLING and within that, ZINT_CSTPORD_ROUTINES.
    The problem
    Currently there is an assumption that every sales order (and its deliveries) will include a product which is made to order, i.e. for which a production order will be required.
    In ZINT_CSTPORD_ROUTINES, a check is made to identify the production order linked to the sales order. If there is no such production order (usually because of the customeru2019s credit status) then processing of the ticket is terminated.
    This assumption would fall down if an order was to be raised (in Command) on which there is no concrete material. For example, if we sold a bag of pigment or a screed to a customer. In this case the item would be sold from stock and there would be no need for a production order.
    The solution
    In the routine which checks for the existence of a production order, modify the code as follows:
    Inspect each item on the sales order
    If (and only if) there is at least one item with a category of u201CZTACu201D then check for a production order, otherwise process the order in the usual manner.
    ----  ZINT_CSTPORD_ROUTINES -
    *&      Form  process_inbound_data
          Create prod. orders from ticket data extracted from the COMMAND
          system. Note that large portions of the code in this routine
          have been copied from the retired ZPPU_COMMAND_PRODUCTION
          interface program. This was done (1) because the old code works
          and (2) to save development time.
         -->T_ZINT_IDATA  Internal table of interface data
         -->T_ZINT_PARAM  Internal table of interface parameters
         -->T_ZINT_MSLOG  Internal table of messages
         -->P_ZINT_ID     Interface ID
         -->P_ZINT_TY     Inteface type
         -->P_ZINT_IS     IDOC group for interface
         -->P_ZINT_DL     Flag: delete IDOC group when complete
         -->P_ZINT_AL     Flag: run in standalone mode
         -->P_ZINT_NW     Flag: do not log warning messages
         -->P_ZINT_SQ     Interface sequence number
         <--P_ZINT_RC     Return code (<>0=>error)
    form process_inbound_data  tables   t_zint_idata structure zint_idata
                                        t_zint_param structure zint_param
                                        t_zint_mslog structure zint_mslog
                               using    p_zint_id    type      zint_id
                                        p_zint_ty    type      zint_ty
                                        p_zint_is    type      zint_is
                                        p_zint_dl    type      zint_dl
                                        p_zint_al    type      zint_al
                                        p_zint_nw    type      zint_nw
                                        p_zint_sq    type      zint_sq
                               changing p_zint_rc    type      zint_rc.
    program is continuing .............
    I WANT TO WRITE A CODING HERE **********************
    CHECK IF PRODUCTION ORDER REQUIRED
              IF NOT THEN GO TO PERFORM UPDATE DATA
      if production order required then check
                    for each item on sales order item list
                          with item category = 'ZTAC' then
                                     return true
                                next
                                  end function
        if there is no production code
               these has to be check from VBAP TABLE field VBELN and PSTYV (ZTAC,ZTAN Etc)
      select * from Vbap WHERE VBELN = '00000269951' and VBAP.PSTYV = 'ZTAC','ZTAN' Etc
    No production order?
        elseif lva_prodord is initial.
          clear v_messg.
          call function 'CONVERSION_EXIT_ALPHA_OUTPUT'
            exporting
              input  = lva_filemat
            importing
              output = lva_filemat.
        No production order found - log a warning message.
          concatenate 'Production Order not be found for'
                      'Command order' lva_cmdord
                      'Material'      lva_filemat
                      'Customer'      lwa_02-customer
            into v_messg separated by space.
          perform write_log_entry
            tables t_zint_mslog
            using  'E' 'ZINT_CSTPORD_ROUTINES'
                       'FIND_SAP_PRODORD'
                         v_messg
                         p_zint_nw
                         lwa_01-ticketnumber.                " RJS
          continue.
        endif.
    Production Order WAS found... Continue creating IDOCS
        lwa_hdrlevel-postg_date = lwa_01-ticketdate.
    Obtain the storage location parameter value.
        read table t_zint_param with key zint_fn = 'LGORT'.
        if sy-subrc ne c_noerr.
          perform write_log_entry
            tables t_zint_mslog
            using  'E' 'ZINT_CSTPORD_ROUTINES'
                       'PROCESS_INBOUND_DATA'
                       'Parameter LGORT is missing from ZINT_PARAM'
                       p_zint_nw
                       lwa_01-ticketnumber.                " RJS
          exit.
        endif.
        loop at l_it_05 into lwa_05
          where ticketnumber = lwa_01-ticketnumber.
          clear lwa_gm_item_create.
          lva_filemat = lwa_05-material.
          if lva_filemat eq lva_prodmat.
            concatenate 'Command ticket-' lwa_05-ticketnumber
              into lwa_hdrlevel-conf_text.
            lwa_hdrlevel-conf_quan_unit = lwa_05-unitofmeasure.
            lwa_hdrlevel-yield          = lwa_05-quantity.
    check whether the confirmed value + current delivery value is equal *
    the production order qty. If the production order value is less
    than the total delivered value, set final conf indicator  and clear
    reservations
            lva_wemng = lva_wemng + lwa_05-quantity.
            if lva_wemng < lva_psmng.
              lwa_hdrlevel-clear_res      = c_false.
              lwa_hdrlevel-fin_conf       = ' '.
            else.
              lwa_hdrlevel-clear_res      = c_true.
              lwa_hdrlevel-fin_conf       = 'X'.
            endif.
            move: 'Z1BP_PP_HDRLEVEL' to t_idoc_data-segnam,
                  lwa_hdrlevel       to t_idoc_data-sdata.
            append t_idoc_data.
            clear lva_formmat.
            lva_formmat                   = lwa_05-material.
            lwa_gm_item_create-material   = lva_formmat.
            lwa_gm_item_create-plant      = lwa_03-plant.
            lwa_gm_item_create-ref_date   = lwa_01-ticketdate.
            lwa_gm_item_create-prod_date  = lwa_01-ticketdate.
            lwa_gm_item_create-move_type  = '101'.
            lwa_gm_item_create-spec_stock = 'E'.
            lwa_gm_item_create-sales_ord  = lva_saleord.
            lwa_gm_item_create-entry_qnt  = lwa_05-quantity.
            lwa_gm_item_create-entry_uom  = lwa_05-unitofmeasure.
            lwa_gm_item_create-orderid    = lva_prodord.
            lwa_gm_item_create-move_mat   = lva_formmat.
            lwa_gm_item_create-move_plant = lwa_03-plant.
            lwa_gm_item_create-mvt_ind    = 'F'.
            clear t_idoc_data.
            move: 'E1BP2017_GM_ITEM_CREATE' to t_idoc_data-segnam,
                  lwa_gm_item_create        to t_idoc_data-sdata.
            append t_idoc_data.
          else.
            clear: lva_loggr,
                   lva_formmat.
            lva_formmat = lwa_05-material.
            select single loggr into lva_loggr from marc
              where matnr = lva_formmat
              and   werks = lwa_03-plant.
            if sy-subrc ne 0.
              clear v_messg.
              No logistics handling group - log a warning message.
              concatenate 'No logistics handling group for material'
                           lva_formmat
                          'in plant'
                           lwa_03-plant
                into v_messg separated by space.
              perform write_log_entry
                tables t_ldata
                using 'W' 'ZINT_CSTPORD_ROUTINES'
                          'PROCESS_INBOUND_DATA'
                          v_messg
                          p_zint_nw
                          lwa_01-ticketnumber.                " RJS
              clear lva_loggr.
            endif.
            if lwa_03-satsur eq 'T'.
              lwa_e1edl21-lprio = 30.
            else.
              lwa_e1edl21-lprio = 20.
            endif.
          else.
            if lwa_03-satsur eq 'T'.
              lwa_e1edl21-lprio = 10.
            else.
              lwa_e1edl21-lprio = '  '.
            endif.
          endif.
          lwa_e1edl21-berot = lwa_04-driver.
          move: 'E1EDL21'   to t_idoc_data-segnam,
                lwa_e1edl21 to t_idoc_data-sdata.
          append t_idoc_data.
          lwa_e1edl55-qualf = '001'.
          lwa_e1edl55-refnr = lva_saleord.
          move: 'E1EDL55'   to t_idoc_data-segnam,
                lwa_e1edl55 to t_idoc_data-sdata.
          append t_idoc_data.
    Loop at materials - create delivery entry for each
          loop at l_it_05 into lwa_05
            where ticketnumber = lwa_01-ticketnumber.
            clear t_idoc_data.
            lwa_e1edl24-matnr = lwa_05-material.
            lwa_e1edl24-werks = lwa_03-plant.
            lwa_e1edl24-vfdat = lwa_01-ticketdate.
            lwa_e1edl24-lfimg = lwa_05-quantity.
            lwa_e1edl24-vrkme = lwa_05-unitofmeasure.
            lwa_e1edl24-lgort = t_zint_param-zint_fv.
            clear lva_loggr.
            lva_formmat = lwa_05-material.
            clear lva_loggr.
            select single loggr into lva_loggr from marc
              where matnr = lva_formmat
              and   werks = lwa_03-plant.
            if sy-subrc ne 0.
            No logistics handling group - log a warning message.
              concatenate 'No logistics handling group for material'
                           lva_formmat
                          'in plant'
                           lwa_03-plant
                into v_messg separated by space.
              perform write_log_entry
                tables t_ldata
                using 'W' 'ZINT_CSTPORD_ROUTINES'
                          'PROCESS_INBOUND_DATA'
                          v_messg
                          p_zint_nw
                          lwa_01-ticketnumber.                " RJS
              lva_loggr = 'BBIN'.
            endif.
            if lva_loggr is initial.
              move: 'E1EDL24'   to t_idoc_data-segnam,
                    lwa_e1edl24 to t_idoc_data-sdata.
              append t_idoc_data.
            endif.
          endloop.
          clear: lva_xabln,
                 lva_vbeln,
                 l_vbfa.
    Matching ticket against a Delivery?
          select single xabln vbeln into (lva_xabln,lva_vbeln) from likp
              where xabln = lwa_01-ticketnumber.
          if sy-subrc = 0.
    If found, does this delivery match the sales order?
            select * from vbfa into l_vbfa
              where vbelv = lva_saleord
              and   vbeln = lva_vbeln.
              exit.
            endselect.
          endif.
    No matching delivery found, or Matching delivery, but for other Sls Ord
          if lva_xabln is initial
          or ( lva_vbeln <> space and l_vbfa is initial ).
            if not lva_saleord is initial.
              perform create_delivery_idocs tables t_zint_mslog
                                            using  s_idcgp
                                                   lwa_01-ticketnumber
                                                   p_zint_nw.
            else.
              concatenate 'Error finding a Sales Order for ticket "'
                          lwa_01-ticketnumber
                          '" reprocess the file AFTER'
                          ' the sales order issues have been fixed'
              into        lva_outtext.
              perform write_log_entry tables t_zint_mslog
                                      using  'E'
                                             'ZINT_CSTPORD_ROUTINES'
                                             'PROCESS_INBOUND_DATA'
                                             lva_outtext
                                             p_zint_nw
                                             lwa_01-ticketnumber. " RJS
            endif.
          else.
            concatenate 'Command Ticket "'
                        lwa_01-ticketnumber
                        '" has already been processed into delivery "'
                        lva_vbeln
            into        lva_outtext.
            perform write_log_entry tables t_zint_mslog
                                    using  'I'
                                           'ZINT_CSTPORD_ROUTINES'
                                           'PROCESS_INBOUND_DATA'
                                           lva_outtext
                                           p_zint_nw
                                           lwa_01-ticketnumber. " RJS
            refresh t_idoc_data.
          endif.
        endif.
        refresh t_idoc_data.
    Write out all messages collected so far
        perform update_data tables t_zint_mslog
                            using p_zint_id p_zint_ty.
      endloop.
    Write out all messages collected so far
      perform update_data tables t_zint_mslog
                          using p_zint_id p_zint_ty.
    endform.                    " process_inbound_data
    Thnaks
    Regards

    Thanks
    Thread closed

  • How to settle the production order variance to 3 GL account

    dear all
    i met a problem in the project ,the customer need see the production order variance category detail for (material,routine,overhead variance) in FI report ,so it need to settle the variance to at least 3 GL account
    i don't know how to configure it ,i try to use result analyse like wip ,but go failed
    do you have some suggestion
    thank you

    Hi ,
    Through Standard SAP .. the same it not possible . Standard SAP will post the differences to one GL account ..The variance amount is not segregated..
    The way out is to use report KKO0  .( Product Costing Drill Down Reports  )  in CO . There are many reports available .. and you can compute the difference in CO Reports and manually make an entry in FI by manually reversing the original variance account and posting it to cost component wise variance accounts ..
    To use the KKO0 report.. please perform the following tasks :-
    1. Assign cost component structure in transaction OKN0 ( Date Extraction/Product Drill Down) tab.
    2.  Product Group Type = Material group..
    3. Run KKRV after period end every month to collect the data for drill down reporting..
    Please revert back for any further clarifications
    Regards
    Sarada
    Sarada

  • How can we delete the production order against sales order

    Dear All
    i

    Dear Gopi,
       In CO02, go to functions tab and select deletion flag active and save the PO. Once you activate the deletion flag GI, release and  operation confirmation will be deactivated.
    See below link to get more understanding.
    Delete Production Order from CO02
    Regards / US

  • How to delete the product?

    Hi Guru’s
    I want to delete product how I can do it?
    E.g.: I Created Product id 3 now I want to delete that Product id 3 so what should I do
    I used Re Categorized products: COMM_PROD_RECATEG but it showing
    So what should I do?
    Regards
    Mahi
    [email protected]

    Hi Mahesh,
    Transaction code for archiving the product master data is SARA. After archiving product, can be deleted.
    Refer the following link here you can find more information on this.
    http://help.sap.com/saphelp_crm50/helpdata/en/d0/493a40a63bc65de10000000a155106/frameset.htm
    The following constraints apply when archiving products in the CRM System:
    · Archived products cannot be reloaded into the CRM System
    · Products can only be deleted if they have been archived
    · Archived products can only be displayed in a technical view in the Archive Information System
    · Inactive products cannot be archived
    · Configurable products cannot be archived
    · Contents of documents are not archived, only the URL is archived
    · Documents and condition records cannot be archived or deleted
    Hope this information helps you.
    With Best Regards
    Nadh.R

  • Deletion of production orders

    Hi All,
               How to delete the production orders in a day from the system

    We use CO78 in a monthly program to set the Status to DLFL.
    The next step is to set the Deletion indcator and then Archive, which will remove the order from the system.
    What exactly do you want to accomplish when you "delete the production orders in a day from the system?"
    Regards

  • How to mass set deletion flag for the production order

    Hi Expert,
      do you know which transcation code or program is used to mass set the deletion flag for production order?
    thank you in advance!

    Hi,
    http://www.sap-img.com/production/how-to-delete-old-production-orders.htm
    Note that CO78 is the start of the Archive process.  We are not using Archiving yet but the initial process fits the bill for what we need to do as mentioned in the original note.
    Decide the range of orders you want to delete.  This range will be used in the program variant. Note that we will be running CO78 many times because of the number of orders involved. 
    Running CO78 calls program PPARCHP1 and this involves the use of a Variant where the parameters for selection etc. are set. 
    First of all, create the variant via SE38 for PPARCHP1. 
    Enter details for number range, order type, plant and set deletion flag. Flag Detailed log and set this to go to Spool when running. Save the variant. You can also force the job to run in background at this point (which I would recommend) via menu line Variant --> Attributes.  Also here you can flag order number, order type and plant to be required fields. 
    Run CO78
    Press the first button - deletion flag/deletion indicator.
    Choose the variant you have just created.  Press "Maintain" to update the selection range on subsequent runs. Save changes and return to initial screen.
    Press Start date to set date and time for job to run as per any background job. Icon will turn Green.
    Press Spool Params to set save output in Spool Q rather than print immediately. Icon will also turn Green.
    Press Execute and job can be tracked via SM37.
    Details of deleted orders and errors will appear in the Spool.
    Rerun as many times as you need with relevant order ranges till all required orders are deleted.
    Hope this will resolve your issue.
    Regards,
    Naveen.

  • Can not delete a Production Order is the Sales order item is rejected?

    Hello everyone,
    I can not delete the production order as the Sales order line item is rejected.
    Does anybody know if any configuration change is required or any work around?
    Thank you,
    BG

    Hi,
    Could you pl. explain how the production order is created?
    Also did you try by choosing Function in the menu (CO02 transaction) & try to set deletion flag or Technically complete?
    If so did you get any error message ?
    Regards,
    Senthilkumar

  • How to delete the PO..?

    Hi all
    Can anybody explain me how to delete the purchase order
    1.Before release ..?
    2.After release..?
    Thanks
    sp-mm

    How to use "me98" to delete PO from system completely?
    I am using "me98"(archive) to delete a PO that have a mistake for vendor code. 
    The following step is: 
    the 1 step: I maintained and saved a variant.  For this variant, I have to create a name for this variant and select the PO which want to delete. it's right? 
    the 2 step: I maintained a "Start Date".  For "Start Date",I select the "immediate " to execute it.  Is it right? 
    the 3 step: whether I maintained the "Spool Params" or not?  May I execute it immediately or not? 
    I have no idea for deleting PO via the "archive".   How can i do that ? 
    Archiving is not deleting. What do you think why SAP developed that much programs to retrieve and read data from an archive. 
    Archiving is saving and keeping data for a certain period (based on local laws for data retention and auditing purposes) outside of the production data base.  Such a job is usually done to keep the database small and fast. 
    While doing archiving the records are written to a file and verified to be readable and then the original record gets deleted from the database. Only if you delete then the file with the archived data you have deleted the record forever. 
    Sometimes people seems to work like a burglar and want erase every single evidence for an error. But even errors, or especially errors are subject to be audited if they are corrected in the right way. This is the same for financial and tax auditiors as for auditors for ISO 9000. 
    To be able to archive, you need to setup the path from SAP to the archive. You need to define the size of your archive and how may records should be kept there. 
    Step 1: Create variant for Archiving. Give it a name. Enter your PO number. Flag One step procedure. Flag detailed log. Erase flag for test run. 
    Step 2: Maintain your start date, you can use Immediate in such a small case. 
    Step 3: Maintain spool parameters. Enter your printer and set the values if you want to print immediatly and if you want keep the print. I suggest to hold the spool in the system. This helps you to determine any error. 
    Step 4. Execute the variant. 
    It creates 4 jobs: 
    ARV_MM_EKKO_SUB...., ARV_MM_EKKO_WRI.... ARV_MM_EKKO_DEL..... 
    ARV_MM_EKKO_STO.... If one of the steps fails, then everything is rolled back, hence nothing is archived, the record is still in your database. In this case use the jobs spool and joblogs to find out what happend.
    http://www.sap-img.com/materials/how-can-we-delete-purchase-requisition.htm
    Regards,
    Ashok

  • Deletion of production order in ECC / APO

    Hi,
    It is not possible to set DLFL (Deletion flag) when the order is in
    CRTD status also when the order is DLV or TECO with no actual cost or open order value .
    It is happening in both the scenarios when
    1. Plan order is created in APO and then converted to prod order
    2. Plan order and prod order both are created in ECC , but both are transferred to APO
    What shall be the process for deleting the prod order in ECC.
    With regards,
    Mrinal

    Hi Mrinal,
    1) You can delete the production order in created status in APO using transaction /n/sapapo/rlcdel, select the required categories for deletion.
    Once the order gets deleted in APO, it will get deleted automatically from ECC also.  If not the transaction /sapapo/ccr to be used which will remove it upon iteration.
    2) Alternatively, if you carry out techo in ECC for a production order which is released, once after delting in ECC, queues needs to be cleared and then subsequently /sapapo/ccr to be run for production orders, so that it will get cleared from APO also upon iteration.
    Please try these and let me know whether your query is resolved.
    Regards
    R. Senthil Mareeswaran.

  • Deletion of Production order

    Hi GURUS,
    I need to know is there any transaction code to delete the production orders.
    Also before I delete production order I need to carry out the below steps,
    Correct the goods movement for the below orders
    Clear all financial postings for below orders
    Ans then to Delete production orders
    Please provide me the step by step explanation for deleting the production orders.
    Awaiting for your reply.
    Cheers,
    Kumar.S

    Hi,
    As mentioned earlier, to set deletion flag on the order, the balance should be zero.
    The balance will be zero, when you reverse out all GI & confirmations if any, or when you settle the order.
    So in this case, go thru' each order & check what has been the GI & what is confirmed, now reverse out the same if it is in the current period, if it is in previous period, then discuss with your FI person.
    To clear recrods from COGI, the user needs authorization for COGI & also for the business transactions which are triggered from COGI, so once you get a error message saying not authorized, ask your basis person to address these issues.
    I doubt there is a simple process for setting deletion flags, simply because you need to understand what has been done & only then suitable actions can be taken. So if you look at it from only system standpoint it would only be a few transactions, but the analysis has to be done from business side, which i guess you've done.
    If you're not sure on the above, first do it in QA, get a sign from business on the same & then do it in PRD system.
    Regards,
    Vivek

Maybe you are looking for

  • Error when connecting to auxiliary instance

    Hi, I have set up an auxiliary database to do a DUPLICATE. The auxiliary instance is started in NOMOUNT mode. When i try to connect from RMAN i get the following error: RMAN>connect auxiliary sys/<password>@<sid> RMAN-00571: =========================

  • Problem in FB60 bapi

    Hi friends , i m developing a prog with bapi of FB60 it always fire the error no 014 i.e. FI/CO interface: Line item entered several times i am feeding the data which is given below in the BAPI . Please help me if anybody has worked on this BAPI w_it

  • How can I repeat a video on my ipad?

    How can I repeat a video on my ipad?  There is no option to repeat videos.

  • BW powered by HANA with ECC integration

    Dear Experts, Kindly help me for step by step BW 7.4 Powerd HANA and ECC system integration & configuration. Regards, Sri.

  • DW's FTP not connecting.

    For about the past month, my Dreamweaver cannot FTP to any of my known sites. I've been using DW for more than 10 years and have worked on multiple sites. I've been using my current install of CS6 DW for more than a year and have not changed any conf