Purchase contract item deletion flag

Hi SAP experts.
By mistake an item line of a purchase contract was flagged for deletion in transaction ME32K, is there a way to remove the flag?
I hope someone can help me.

Hi
Go into Contract in change mode (ME32K)
Select the line item,
Edit--> Reset deletion indicator and SAVE.
Thanks
Sasi

Similar Messages

Regarding purchase order header deletion flag indicator

hi all,
Right now in SAP PO header deletion flag has been set to X.
so what i need is the PO should be flagged only at item level .
how can i proceed?where can i find the deletion flag in the transaction screen?

You can find in item overview (RM06E-LOEKZ)
a®

Reg:purchase order header deletion flag

hi all,
right now in SAP PO header deletion flag has been set to X.
so what i need is the PO should be flagged only at item level .
how can i proceed?where can i find the deletion flag in the transaction screen?

Hi,
To set deletion flag at PO item, select the item and click on delete icon (a garbage bin).
Cheers.
...Reward if useful.

Problem with Purchase Contract Item Price - 2lis_02_itm

Hello !
I used 2lis_02_itm extractor in order to extract the Purchase contracts (transaction me33k in R/3) with Item Prices. The problem is that the extractor takes the price
from ekpo table but the Contract item prices exist in konp table and its very complicate to calculate the net price.
Somebody know the solution ?
Thanks In advance,
MM. michal

Thanks for your answer.
I found out that all the subtotal1-6 are empty in my extractor.
If you interest I found in R3 transaction ME3P
That update the prices from konp in EKPO and all my problems solved.
Again thanks , michal

User-exit/BADI to change Purchase Contract item field ??

Hello,
I need to update the Order acknowledgement field(EKPO-KZABS) for the Purchase contract via transaction ME32K.
I need to know if there is any user exit or BADI for the Purchase contracts (Outline agreement), so that this field KZABS can be updated while saving. I did not find any user exit so far in which line item is a export parameter. There is one BADI definition ME_PROCESS_PO_CUST but it is called only in case of Purchase Orders and not in the contracts. Please let me know if you have some idea how to do this.

check these exits....
EXIT_SAPMM06E_012
<b>EXIT_SAPMM06E_013</b>
EXIT_SAPMM06E_014
EXIT_SAPMM06E_006
EXIT_SAPMM06E_007
EXIT_SAPMM06E_018
EXIT_SAPMM06E_016
EXIT_SAPMM06E_017
vijay

Item Deletion Flag

Dear Mentors
Where i can check item deletion fiag (mm06) whether item flag is active or not ?
Regards
Laxman

Hi,
You can check it in MM06 one-by-one.
If you have several goods to be checked you have to use SE16 (to check tables) or SQVI (to create query using two or more tables).
Since you can mark a material with DF at different organisational levels, you have to use the appropriate material master tables tables.
E.g. if you marked your goods at client level the DF can be found in table MARA (MARA-LVORM). If you marked your goods at plant level, try table MARC (LVORM). You can use DF at SLoc level, WH level, etc...
BR
Csaba

Purchase Order Item deleted; purchase requsition quantity not update

Hello,
We have PR-20025224 item 130 the quantity ordered is 200 on 2 PO 4200039509 and 4200083799 (100 each)
One of the PO (4200083799) is deleted (No GR)so the quantity ordered should be 100 only in the purchase requisition u201CStatusu201D tab.
Normally the program RM06HL04 should correct the quantity ordered but it does not.
In the status tab in purchase requistion details are as below
Proc Status:- B PO Created
Block ID - Not Blocked
Ord Qty - 200
- 05 Relese Completed
Thanks to help me in this issue.

Hello Jurgen,
Thanks a lot for the reply.
I checked the deleted PO, in "Delivery Schedule" tab at right end the last column is "PReq Closed" and it is blanked.
Actually the client need is, once the PO deleted, in the purchase requistion "Status" tab "Ord Qty" gets changed (In this case it should reduce by 100 no from 200 nos, because other PO is for 100 nos)
But PR Ord Qty does not changed.
Is it possible that, the PR quantity gets changed once PO deleted?
Thanks for the reply and hep.
Hemant

Allow to create a purchase order with purchase requisiton item deleted

Dear all,
I have a question about creation purchase order process.
Firstly, I have a purchase requisition with 2 items, first of them is deleted.
If I try to create a purchase order thru transaction ME57N with the previous purchase requisition, I can only create it with one item (the one wich is not deleted)
However, if I try to create the purchase order thru transaction ME21N, with purchase requisition as reference, I can create the PO with item that was deleted in PR.
I don't understand why system allows to create a purchase order with an item that previously was deleted in PR.
Does anyone have a explanation about this issue?
Many thanks in advance
Best Regards.

Hi,
In the document overview of ME21N you get all the items of the purchase
requisitions, no matter if they are deleted or not.
When you convert the deleted item into a Purchase Order you get message
06 050 stating that this item is deleted in the purchase requisition.
This message can be defined as an error message in the customizing
transaction OME0. This way, it will not be possible to order an item
which is deleted in the referenced purchase requisition.
BR
Nadia Orlandi

BAPI to change purchase order to put deletion flag

Hello Guru's,
        We are about to archive data & for that we need that according to date range all open purchase order ,open purchase requsitions & open RFQ should be marked for deletion.
Is there some BAPI to do so.Please guide.

*DELETING FLAG *
REPORT ZMMR_DELETEPO NO STANDARD PAGE HEADING MESSAGE-ID zisb.
tables : zvtls_sap.
*C-- Types Declarations
TYPES : BEGIN OF tp_flatfile_vtls,
        ebeln(10),
        ebelp type ekpo-ebelp,
        END OF tp_flatfile_vtls.
*=====================================================================
                  INTERNAL TABLES DECLARATION
*=====================================================================
DATA: t_flatfile_vtls TYPE tp_flatfile_vtls OCCURS 0 WITH HEADER LINE.
data : begin of t_sapdata occurs 0,
       po like zvtls_sap-posap,
       item like zvtls_sap-itemsap,
       end of t_sapdata.
data : begin of t_flatfile_vtls1 occurs 0,
       po(10),
       item like zvtls_sap-itemsap,
       end of t_flatfile_vtls1.
data : begin of t_update occurs 0,
       mandt like zvtls_sap-mandt,
       povtls like zvtls_sap-povtls,
       itemvtls like zvtls_sap-itemvtls,
       posap like zvtls_sap-posap,
       itemsap like zvtls_sap-itemsap,
       aedat like zvtls_sap-aedat,
       paedt like zvtls_sap-paedt,
       loekz like zvtls_sap-loekz,
       end of t_update.
data : begin of t_poheader occurs 0,
       po like zvtls_sap-posap,
       end of t_poheader.
data : begin of t_poitem occurs 0,
       po like zvtls_sap-posap,
       item like zvtls_sap-itemsap,
       end of t_poitem.
DATA : BEGIN OF T_MESSAGE OCCURS 0,
       MSGTY,
       MSGID(2),
       MSGNO(3),
       MSGTX(100),
       PO like zvtls_sap-povtls,
       item like zvtls_sap-itemvtls,
       END OF T_MESSAGE.
DATA : BEGIN OF t_bapi_poheader OCCURS 0.
        INCLUDE STRUCTURE bapimepoheader.
DATA : END OF t_bapi_poheader.
DATA : BEGIN OF t_bapi_poheaderx OCCURS 0.
        INCLUDE STRUCTURE bapimepoheaderx.
DATA : END OF t_bapi_poheaderx.
DATA : BEGIN OF t_bapi_poitem OCCURS 0.
        INCLUDE STRUCTURE bapimepoitem.
DATA : END OF t_bapi_poitem.
DATA : BEGIN OF t_bapi_poitemx OCCURS 0.
        INCLUDE STRUCTURE bapimepoitemx.
DATA : END OF t_bapi_poitemx.
DATA : BEGIN OF t_bapireturn OCCURS 0.
        INCLUDE STRUCTURE bapiret2.
DATA : END OF t_bapireturn.
*=====================================================================
                  V A R I A B L E S
*=====================================================================
DATA: w_success(6) TYPE n,
      w_bklas like t023-bklas,
      w_curryear(4),
      w_begda like sy-datum,
      w_endda like sy-datum,
      w_begyr(4),
      w_endyr(4),
      w_currmon(2),
      w_assetclass like ankt-anlkl,
      w_price type p,
      w_recordsap type i,
      w_povtls(10),
      w_count type i.
DATA: w_filepath TYPE rlgrap-filename,
       w_rc TYPE sy-subrc,
       w_sscrfields_ucomm1   TYPE sscrfields-ucomm,
       w_file1 TYPE string,
       w_file2 TYPE FILENAME-FILEINTERN.
*=====================================================================
                  C O N S T A N T S
*=====================================================================
CONSTANTS: c_x              TYPE c         VALUE 'X',
           c_hyp            TYPE c         VALUE '-',
           c_err            TYPE bdc_mart VALUE 'E'.
CONSTANTS: c_slash(1)            TYPE c VALUE '/',
            c_hash(1)             TYPE c VALUE '#',
            c_pipe                TYPE c VALUE '|',
            c_1                   TYPE i VALUE 1,
            c_zero                TYPE n VALUE '0',
            c_rg1(3)              TYPE c VALUE 'rg1',
            c_gr3(3)              TYPE c VALUE 'GR3',
            c_gr2(3)              TYPE c VALUE 'GR2',
            c_e(1)                TYPE c VALUE 'E',
            c_filepath(8)         TYPE c VALUE '/interf/',
            c_filetype(10)        TYPE c VALUE 'ASC'.
CONSTANTS : c_bapimepoheaderx   TYPE x030l-tabname
                               VALUE 'bapimepoheaderx',
           c_bapimepoitem      TYPE x030l-tabname
                               VALUE 'bapimepoitem',
           c_bapimepoaccount   TYPE x030l-tabname
                               VALUE 'bapimepoaccount',
           c_t_bapi_poheader(15)        TYPE c
                                        VALUE 't_bapi_poheader',
           c_t_bapi_poitem(13)          TYPE c
                                        VALUE 't_bapi_poitem',
           c_t_bapi_poitemx(14)         TYPE c
                                        VALUE 't_bapi_poitemx',
           c_t_bapi_poheaderx(16)       TYPE c
                                        VALUE 't_bapi_poheaderx'.
CLASS cl_abap_char_utilities DEFINITION LOAD.
CONSTANTS:con_tab TYPE c VALUE cl_abap_char_utilities=>horizontal_tab.
*======================================================================
                       SELECTION SCREEN
*======================================================================
SELECTION-SCREEN BEGIN OF BLOCK inputpath WITH FRAME TITLE text-001.
SELECTION-SCREEN : BEGIN OF BLOCK blk2 WITH FRAME TITLE text-002.
PARAMETERS : p_fore RADIOBUTTON GROUP rg1
                    USER-COMMAND pc,
             p_back RADIOBUTTON GROUP rg1 DEFAULT 'X'.
SELECTION-SCREEN : END OF BLOCK blk2.
SELECTION-SCREEN : BEGIN OF BLOCK blk1 WITH FRAME TITLE text-003.
PARAMETERS : p_file1 LIKE rlgrap-filename OBLIGATORY MODIF ID gr2.
PARAMETERS : p_afile1 LIKE rlgrap-filename OBLIGATORY MODIF ID gr3.
SELECTION-SCREEN : END OF BLOCK blk1.
SELECTION-SCREEN END OF BLOCK inputpath.
*C-- Initialization Event
INITIALIZATION.
CLEAR w_filepath.
CONCATENATE c_filepath sy-sysid c_slash sy-mandt c_slash INTO
w_filepath.
CONDENSE w_filepath NO-GAPS.
p_file1 = text-008.
p_afile1 = text-009.
*======================================================================
                       SELECTION SCREEN EVENTS
*======================================================================
*C-- Selection Screen Output
AT SELECTION-SCREEN OUTPUT.
IF p_fore = c_x.
    w_sscrfields_ucomm1 = space.
ELSE.
    w_sscrfields_ucomm1 = c_rg1.
ENDIF.
LOOP AT SCREEN.
*C--Modify selection screen if presentation
*C--or application server radio button is chosen
    IF w_sscrfields_ucomm1 = space.
      IF screen-group1 = c_gr3.
        screen-active = c_zero.
      ENDIF.
    ELSE.
      IF screen-group1 = c_gr2.
        screen-active = c_zero.
      ENDIF.
    ENDIF.
    if screen-name = 'P_AFILE1'.
      screen-input = 0.
    ENDIF.
    MODIFY SCREEN.
ENDLOOP.
*C-- Selection Screen VALUE-REQUEST FOR File path
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file1.
IF p_fore EQ c_x.
    CALL FUNCTION 'F4_FILENAME'
      EXPORTING
        program_name = syst-cprog
        dynpro_number = syst-dynnr
      IMPORTING
        file_name     = p_file1.
ENDIF.
*C-- At Start of the Selection Process
START-OF-SELECTION.
IF p_fore EQ c_x.
    w_file1 = p_file1.
ELSE.
    w_file2 = p_afile1.
ENDIF.
IF p_fore EQ c_x. " Presentaion Server
*C--Validations for the input files
    PERFORM validate_pre_file USING p_file1.
*C-- Load the contents of the input file into the internal table
    PERFORM upload_file TABLES t_flatfile_vtls
                        USING w_file1
                        CHANGING w_rc.
    IF w_rc <> 0.
      MESSAGE s006 DISPLAY LIKE c_e.
    ENDIF.
ELSE. " Application Server
*C--Validations for the input files
    PERFORM validate_app_file USING w_file2.
*C-- Load the contents of the input file into the internal table
    PERFORM upload_file_app TABLES t_flatfile_vtls
                            USING w_file2
                            CHANGING w_rc.
ENDIF.
loop at t_flatfile_vtls.
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
      EXPORTING
        input = t_flatfile_vtls-ebeln
      IMPORTING
        output = t_flatfile_vtls1-po.
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
      EXPORTING
        input = t_flatfile_vtls-ebelp
      IMPORTING
        output = t_flatfile_vtls1-item.
    append t_flatfile_vtls1.
    clear t_flatfile_vtls1.
endloop.
perform get_podata.
loop at t_poheader.
    perform move_to_bapi.
    perform call_bapi.
endloop.
PERFORM STORE_MESSAGES TABLES T_MESSAGE.
*&      Form validate_pre_file
    Routine to validate presentation server file path.
     -->fp_name text
FORM validate_pre_file USING fp_name TYPE rlgrap-filename.
DATA : l_result,
         l_filename TYPE string.
l_filename = fp_name.
CLEAR l_result.
CALL METHOD cl_gui_frontend_services=>file_exist
    EXPORTING
      file                 = l_filename
    RECEIVING
      result               = l_result
    EXCEPTIONS
      cntl_error           = 1
      error_no_gui         = 2
      wrong_parameter      = 3
      not_supported_by_gui = 4
      OTHERS               = 5.
IF sy-subrc <> 0.
    MESSAGE s007 DISPLAY LIKE c_e.
    LEAVE LIST-PROCESSING.
ELSEIF l_result IS INITIAL.
    MESSAGE s008 DISPLAY LIKE c_e.
    LEAVE LIST-PROCESSING.
ENDIF.
ENDFORM.                    " validate_pre_file_hdr
*&      Form validate_app_file
      text - Checks if the path entered and filename is correct
FORM validate_app_file USING fp_file TYPE FILENAME-FILEINTERN.
data : l_fname(60).
CALL FUNCTION 'FILE_GET_NAME'
    EXPORTING
      LOGICAL_FILENAME = FP_FILE
      OPERATING_SYSTEM = SY-OPSYS
    IMPORTING
      FILE_NAME        = L_FNAME
    EXCEPTIONS
      FILE_NOT_FOUND   = 1
      OTHERS           = 2.
IF SY-SUBRC = '0'.
    OPEN DATASET L_FNAME FOR INPUT IN TEXT MODE ENCODING DEFAULT.
    IF sy-subrc NE 0.
      MESSAGE s007 DISPLAY LIKE c_e.
    ELSE.
      CLOSE DATASET l_fname.
    ENDIF.
ENDIF.
ENDFORM.                    " validate_app_file
*&      Form upload_file
      Routine to upload data from file to tables.
     -->P_fp_flatfile
     -->P_fp_file
     <--P_fp_rc
FORM upload_file TABLES   fp_flatfile
                  USING    fp_file TYPE string
                  CHANGING fp_rc TYPE sy-subrc.
IF fp_flatfile[] IS INITIAL.
    CALL FUNCTION 'GUI_UPLOAD'
      EXPORTING
        filename                = fp_file
        filetype                = c_filetype
        has_field_separator     = c_x
      TABLES
        data_tab                = fp_flatfile
      EXCEPTIONS
        file_open_error         = 1
        file_read_error         = 2
        no_batch                = 3
        gui_refuse_filetransfer = 4
        invalid_type            = 5
        no_authority            = 6
        unknown_error           = 7
        bad_data_format         = 8
        header_not_allowed      = 9
        separator_not_allowed   = 10
        header_too_long         = 11
        unknown_dp_error        = 12
        access_denied           = 13
        dp_out_of_memory        = 14
        disk_full               = 15
        dp_timeout              = 16
        OTHERS                  = 17.
    MOVE sy-subrc TO fp_rc.
ENDIF.
ENDFORM. " upload_file
*&      Form upload_file_app
      text
     -->FP_FLATFILEtext
     -->FP_FILE    text
     -->FP_RC      text
FORM upload_file_app TABLES   fp_flatfile
                      USING    fp_file TYPE FILENAME-FILEINTERN
CHANGING fp_rc TYPE sy-subrc.
DATA: l_string TYPE tedata-data.
DATA: wa_data_file TYPE tp_flatfile_vtls,
        l_wllength TYPE i,
        FNAME(60).
CALL FUNCTION 'FILE_GET_NAME'
    EXPORTING
      LOGICAL_FILENAME = FP_FILE
      OPERATING_SYSTEM = SY-OPSYS
    IMPORTING
      FILE_NAME        = FNAME
    EXCEPTIONS
      FILE_NOT_FOUND   = 1
      OTHERS           = 2.
IF SY-SUBRC = 0.
    OPEN DATASET FNAME FOR INPUT IN TEXT MODE ENCODING DEFAULT.
    IF sy-subrc NE 0.
*C-- commented by Bikash
     MESSAGE s107(yaero_ps) DISPLAY LIKE c_e.
      message e008.
    ELSE.
      DO.
        CLEAR: l_string.
        READ DATASET FNAME INTO l_string LENGTH l_wllength.
        IF sy-subrc NE 0.
          EXIT.
        ELSE.
          SPLIT l_string AT con_tab INTO   wa_data_file-ebeln
                                           wa_data_file-ebelp.
          APPEND wa_data_file TO fp_flatfile.
        ENDIF.
      ENDDO.
      CLOSE DATASET FNAME.
    ENDIF.
ENDIF.
ENDFORM. " upload_file_app
*&      Form get_podata
      text
form get_podata.
select *
into table t_update
from zvtls_sap
for all entries in t_flatfile_vtls1
   where itemvtls = t_flatfile_vtls1-item
and povtls = t_flatfile_vtls1-po.
sort t_update by posap itemsap.
loop at t_update.
    at new posap.
      t_poheader-po = t_update-posap.
      append t_poheader.
      clear t_poheader.
    endat.
    t_poitem-po = t_update-posap.
    t_poitem-item = t_update-itemsap.
    append t_poitem.
    clear t_poitem.
    t_update-paedt = sy-datum.
    t_update-loekz = 'X'.
    modify t_update.
endloop.
modify zvtls_sap from table t_update.
endform.                    "get_podata
*&      Form move_to_bapi
      text
form move_to_bapi.
t_bapi_poheader-po_number = t_poheader-po.
CLEAR t_bapi_poheaderx.
PERFORM fill_check_structure USING c_bapimepoheaderx
                                     c_t_bapi_poheader
                                     c_t_bapi_poheaderx
                                     c_x.
refresh : t_bapi_poitem,t_bapi_poitemx.
loop at t_poitem where po = t_poheader-po.
    clear t_bapi_poitem.
    t_bapi_poitem-po_item = t_poitem-item.
    t_bapi_poitem-delete_ind = 'X'.
    CLEAR t_bapi_poitemx.
    PERFORM fill_check_structure USING c_bapimepoitem
                                       c_t_bapi_poitem
                                       c_t_bapi_poitemx
                                       c_x.
    t_bapi_poitemx-po_item = t_poitem-item.
    t_bapi_poitemx-po_itemx = c_x.
    APPEND t_bapi_poitem.
    APPEND t_bapi_poitemx.
    clear t_bapi_poitem.
    clear t_bapi_poitemx.
endloop.
endform.                    "move_to_bapi
*&      Form call_bapi
      This form Routine is used to commit the data records
FORM call_bapi .
DATA : l_msgty      TYPE c,
         l_msgid(2)   TYPE c,
         l_msgno(3)   TYPE c,
         l_msgtx(100) TYPE c,
         l_errflag    TYPE c.
CLEAR: t_bapireturn.
REFRESH: t_bapireturn.
*CALL FUNCTION 'BAPI_PO_CHANGE'*
    EXPORTING
      PURCHASEORDER = T_POHEADER-PO
      POHEADER      = T_BAPI_POHEADER
      POHEADERX     = T_BAPI_POHEADERX
    TABLES
      RETURN        = T_BAPIRETURN
      POITEM        = T_BAPI_POITEM
      POITEMX       = T_BAPI_POITEMX.
READ TABLE t_bapireturn WITH KEY type = c_err TRANSPORTING NO FIELDS.
IF sy-subrc NE 0.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
      EXPORTING
        wait = c_x.
ENDIF.
*C-- Write messages
WRITE: / 'PO Number', t_poheader-po.
clear : t_update,w_povtls.
read table t_update with key posap = t_poheader-po.
w_povtls = t_update-povtls.
CLEAR l_errflag.
LOOP AT t_bapireturn.
    CLEAR: l_msgty, l_msgid, l_msgno, l_msgtx.
    l_msgty = t_bapireturn-type.
    l_msgid = t_bapireturn-id.
    l_msgno = t_bapireturn-number.
    l_msgtx = t_bapireturn-message.
    WRITE: / l_msgty, l_msgid, l_msgno, l_msgtx.
    if l_msgtx cs t_poheader-po.
      w_count = w_count + 1.
      loop at t_update.
        if sy-tabix = w_count.
          t_message-item = t_update-itemvtls.
        endif.
      endloop.
    endif.
    t_message-msgty = l_msgty.
    t_message-msgid = l_msgid.
    t_message-msgno = l_msgno.
    t_message-msgtx = l_msgtx.
    t_message-po = w_povtls.
    append t_message.
    clear t_message.
    IF l_msgty EQ c_err.
      l_errflag = c_x.
    ENDIF.    " l_msgty EQ 'E'
ENDLOOP.
ULINE.
IF l_errflag NE c_x.
    w_success = w_success + 1.
ENDIF.    " l_errflag NE C_X
endform.                    "call_bapi
*&      Form fill_check_structure
      This form Routine will check whether the specified structure
      exist/active
FORM fill_check_structure USING    fp_tabname TYPE any
                                    fp_orgtabname TYPE any
                                    fp_chktabname TYPE any
                                    fp_check TYPE c.
FIELD-SYMBOLS : <fs_chk>, <fs_org>.
DATA:    l_char1(61) TYPE c,
           l_char2(61) TYPE c.
DATA:    BEGIN OF tl_nametab OCCURS 60.
          INCLUDE STRUCTURE x031l.
DATA:    END OF tl_nametab.
REFRESH tl_nametab.
CALL FUNCTION 'RFC_GET_NAMETAB'
    EXPORTING
      tabname          = fp_tabname
    TABLES
      nametab          = tl_nametab
    EXCEPTIONS
      table_not_active = 1
      OTHERS           = 2.
IF sy-subrc <> 0.
    CLEAR tl_nametab.
ENDIF.
LOOP AT tl_nametab.
    CLEAR: l_char1, l_char2.
    CONCATENATE fp_chktabname c_hyp tl_nametab-fieldname INTO l_char1.
    ASSIGN (l_char1) TO <fs_chk>.
    CONCATENATE fp_orgtabname c_hyp tl_nametab-fieldname INTO l_char2.
    ASSIGN (l_char2) TO <fs_org>.
    IF <fs_org> IS NOT INITIAL.
      <fs_chk> = fp_check.
    ENDIF.
ENDLOOP.
ENDFORM.                    " fill_check_structure
*&      Form STORE_MESSAGES
      text
     -->FP_MESSAGEStext
FORM STORE_MESSAGES TABLES FP_MESSAGES STRUCTURE T_MESSAGE.
DATA: wl_output_data LIKE t_MESSAGE.
DATA: l_catstr TYPE string.
DATA: l_fieldvalue TYPE string.
DATA: l_index TYPE i VALUE 1.
DATA: L_FNAME(60).
FIELD-SYMBOLS <fs>.
CLEAR l_catstr.
CALL FUNCTION 'FILE_GET_NAME'
    EXPORTING
      LOGICAL_FILENAME = '/USR/SAP/VTLS/POCHANGE/LOG'
      OPERATING_SYSTEM = SY-OPSYS
    IMPORTING
      FILE_NAME        = L_FNAME
    EXCEPTIONS
      FILE_NOT_FOUND   = 1
      OTHERS           = 2.
IF SY-SUBRC = '0'.
    IF fp_messages[] IS NOT INITIAL.
      OPEN DATASET L_FNAME FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
      IF sy-subrc NE 0.
        LEAVE LIST-PROCESSING.
      ELSE.
        LOOP AT fp_messages INTO wl_output_data.
          DO.
           ASSIGN COMPONENT l_index OF STRUCTURE wl_output_data TO <fs>.
            IF sy-subrc <> 0.
              EXIT.
            ENDIF.
            MOVE <fs> TO l_fieldvalue.
            IF l_catstr IS NOT INITIAL.
              CONCATENATE l_catstr l_fieldvalue INTO l_catstr SEPARATED
              BY con_tab.
            ELSE.
              MOVE l_fieldvalue TO l_catstr.
            ENDIF.
            l_index = l_index + c_1.
            CLEAR l_fieldvalue.
            CLEAR <fs>.
          ENDDO.
          l_index = c_1.
          TRANSFER l_catstr TO L_FNAME .
          CLEAR wl_output_data.
          CLEAR l_catstr.
        ENDLOOP.
        CLOSE DATASET L_FNAME.
      ENDIF.
    ENDIF.
ENDIF.
ENDFORM.                    "STORE_MESSAGES

Purchase contract print preview is displaying items with DEL_IND='X'

Hi,
We are using SRM Server 5.5 and have a situation described below
A purchasing contract is created with, for example, 2 items with status as 'Held' . In change mode, the one item is deleted and the purchasing contract is Released.
When the button 'Output Preview' is pressed, the system displays the print preview with both the irems although one item is deleted.
I am trying to find SAP notes for this but I didn't find any relavent note.
I found one note for not displaying 'Inactive' status items however not found anything for excluding deleted items from print preview.
Appreciate your inputs on this.
Thanks and Regards,
Sambhaji Chawale

Thanks Georg for your inputs.
Yes, you are correct we are using custom developed smart form and not SAP Standard. We will be updating the smartform for adding the condition of u201Cselect items with deletion indicator=u2019Blanku2019.
However we are interested in the standard solution that SAP has provided to cover this. I don't see this condition in SAP standard smart form so this must have been covered through some program code.
Does anybody have idea on this.
Thanks and Regards,
Sambhaji Chawale

Purchase Contract Price on line item

Scenario
Purchase contract line item has conditions defined with multiple validity periods and scales for the price.
When one uses transaction ME33K one sees the net price applicable on the current date. and this is not what is stored in the EKPO-NETPR.
Needless to say the condition amounts and scales amounts can be defined in a different UoM from the contract line item Order Unit.
Is there a FM which enables you to get the current Net Price of the Contract line item?
Gurus please respond.

Dear Lin,
I'm looking for a solution in SAP for the following:
If I make a change in contracts or purchase info records in SAP (for instance in prices) is there any way to update the open Purchase orders in the system with this information?
As this question is relevant to what you asked I thought that you may have a clue about this.
Thanks for your attention,
Marc Fabiá

Purchase Requistion item is not showing deleted.

CJ20N............we have deleted the material from the network for purchase requsition......... but that items is not shown deleted in purchase requisition in ME52N....
Line item in p. req. change mode has been greyed out......and not showing deleted........
Plz. help..........
Rgds,
Navin

Hi Naveen ,
Sometimes inconsistencies do occur in the database tables .
for your issue in question , you can go to SE38 Transaction and type in the Program name
RLORD035 and test .
--- Correction Rpt : Inconsistancy in Purchase Req. Deletion Indic./ Order
Enter the Purchase Requistion No. in question and you can run that in test mode .
Any inconsistancies will be shown and you can execute the actual run , ticking the checkbox " Set Deletion Indicator "
Hope that helps .
Kish

How can i delete Purchase Requisition item

how can i delete Purchase Requisition item
can any one hepl me
thanks in advanced.

Deleting a PR item in then sense via transaction or program.
If itz transaction, you can use transaction ME52N.
1. Go the PR via transction ME52N
2. Select the respective item, and click on TRASH BIN button i.e delete button from the above icons.
If you want to do it programmatically,maybe you can use: BAPI_PR_CHANGE for the same.
Kind Regards
Eswar

Batch deletion flag - Purchase order

Dear all,
even if I set in batch master the deletion flag at a plant level (MCHA-LVORM) I can create a Purchase order. No message are displayed (warning or error).
Only when I post the good receipt, an error message occurs (M7 144).
How can I prevent to use a deleted batch in PO?
Thanks
Marco

Hi,
mark the deletion or restrict batch for flag in MSC2N, after that change the mesage type M7 144
in OPK9 also check your valuation area.
Regards
Raj.

Purchasing info record 5300000013 flagged for deletion

Hi,
While changing the Purchasing info record , we get the following message:
Purchasing info record 5300000013 flagged for deletion as a warning
We want to convert this message as error. For that we changed the System message category, purchasing as "E" in Materials Management-> Purchasing-> Environment Data-> Define Attributes of System Messages, but after that also the System gives a warning message in T Code ME12.
Where do I need to change to get the error message? As per understanding, the system should always warning message so that we can change the deletion flag, if required in future.
Please guide.
Regards,
PK

hi,
Try to understand the importance of the message. PIR document is not must to make or create any PO...
but in case if req. or for copying few parameters from old/latest PIR, we use it...
Its always better to have the PIR for the PO, which may be made before or after the generation PO...as it stores the PO price history, conditions etc...which may get updated and pulled whenever required...
So, due to such reasons system has made this message as warning message...because you can use it just for record maintainance, but it will be of no use if thinking practically...
Normally we make these settings at SPRO >> IMG>>MM Purchasing>>Environment data>> Define attributes of system messages...
Regards
Priyanka.P

Purchase contract item deletion flag

Similar Messages

Maybe you are looking for