PReq 1100000000/ not convertible (status )

while creating RFQ with reference of PR iam getting this error
PReq 1100000000/ not convertible (status )
Pls guide...

Hi
This is manual PR only i have created for 150 qty,
i have activated version management also to check that i tried changing it by 200 qty, Now it is version 1
first when you create PR for 150 qty ,version was 0
now you change quality 200 means version is created 1,but this version not completed i think
as you said version in process,please check in PR at left hand side , version complete flag active or not,If not active it manually
Regards
Kailas Ugale

Similar Messages

ISE 1.2 - Posture Detail Assessment - enforcement audit mode report not show status for non-compliant

ISE 1.2 - Posture Detail Assessment - enforcement audit mode report not show status for non-compliant.
- For old version 1.1.4 it can be reported for non-compliant, How can I generate report for this?
Thanks
Kosin Usuwanthim

It used to be in there (id 226635 is the last one with it); should I clean it up a bit and put it back with a bit more of a disclaimer?

Error-IM258-Object does not exist (Status Management)

Dear All
We have used the enhancement "MCI10001" for triggering the external E mail while scheduling the maintenance plan using T code IP10.
System will fetch the E mail ID from the equipment master -partner function either Vendor or User responsible and sends the mail
But while executing IP10 system throws an error message as follows
Error Msg no: IM 258- Object does not exist (Status Management)
This refers to an error in central status management.
Kindly help on the above issue
Regards
Thyagarajan

l have same problem my code below
help me please .
if email is not INITIAL and ulke is not initial and sy-tcode eq 'QM01' and sy-ucomm eq 'BUCH' and I_VIQMEL-QMART = 'Q1'.
    CALL FUNCTION 'POPUP_TO_CONFIRM'
      EXPORTING
        TITLEBAR       = 'E-mail'
        TEXT_QUESTION = 'E-mail Göndermek istiyormusunuz ?'
      IMPORTING
        ANSWER         = answer
      EXCEPTIONS
        TEXT_NOT_FOUND = 1
        OTHERS         = 2.
if answer eq 1 and ulke = 'TR'.
lt_mailtxt ='Değerli Müşterimiz,'.
APPEND lt_mailtxt.clear lt_mailtxt.
lt_mailtxt = 'Şikayetiniz sistemimize alınmıştır. Müşteri şikayeti sorumlularımız sizlerle en yakın zamanda irtibata '.
APPEND lt_mailtxt.clear lt_mailtxt.
lt_mailtxt = 'geçeceklerdir. Şikayetiniz için teşekkür eder, saygılarımızı sunarız.'.
APPEND lt_mailtxt.clear lt_mailtxt.
lt_mailtxt =''.
APPEND lt_mailtxt.clear lt_mailtxt.
data: it_packing_list like sopcklsti1 occurs 0 with header line,
       it_receivers like somlreci1 occurs 0 with header line,
        gd_cnt type i,
        gd_sent_all(1) type c,
        gd_doc_data like sodocchgi1,
        gd_error type sy-subrc.
gd_doc_data-doc_size = it_packing_list-body_num * 255.
Populate the subject/generic message attributes.
gd_doc_data-obj_langu = sy-langu.
gd_doc_data-obj_name = 'SAPRPT'.
gd_doc_data-obj_descr = 'Naksan KGM'.
gd_doc_data-sensitivty = 'F'.
Describe the body of the message
clear it_packing_list.
refresh it_packing_list.
it_packing_list-transf_bin = space.
it_packing_list-head_start = 1.
it_packing_list-head_num = 0.
it_packing_list-body_start = 1.
describe table lt_mailtxt lines it_packing_list-body_num.
it_packing_list-doc_type = 'RAW'.
append it_packing_list.
CLEAR it_receivers.
it_receivers-receiver = email.
it_receivers-rec_type = 'U'.
it_receivers-com_type = 'INT'.
it_receivers-notif_del = 'X'.
it_receivers-notif_ndel = 'X'.
append it_receivers.
call function 'SO_DOCUMENT_SEND_API1'
       exporting
            document_data              = gd_doc_data
            put_in_outbox              = 'X'
            sender_address             = 'sinan.tataroglu@***.com'
            sender_address_type        = 'INT'
            commit_work                = 'X'
       importing
            sent_to_all                = gd_sent_all
       tables
            packing_list               = it_packing_list
            contents_txt               = lt_mailtxt[]
            receivers                  = it_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.
IF sy-subrc EQ 0.
COMMIT WORK.
Push mail out from SAP outbox.
SUBMIT rsconn01 WITH mode = 'INT' AND RETURN.
ENDIF.
elseif ulke ne 'TR' and answer eq 1.
lt_mailtxt ='Dear Customer,'.
APPEND lt_mailtxt.clear lt_mailtxt.
lt_mailtxt = 'Your compliant has just entered to system. Customer complaint responsible will contact with you ASAP.'.
APPEND lt_mailtxt.clear lt_mailtxt.
lt_mailtxt = 'Thanks for your complaint.'.
APPEND lt_mailtxt.clear lt_mailtxt.
gd_doc_data-doc_size = it_packing_list-body_num * 255.
Populate the subject/generic message attributes
gd_doc_data-obj_langu = sy-langu.
gd_doc_data-obj_name = 'SAPRPT'.
gd_doc_data-obj_descr = 'Naksan KGM'.
gd_doc_data-sensitivty = 'F'.
Describe the body of the message
clear it_packing_list.
refresh it_packing_list.
it_packing_list-transf_bin = space.
it_packing_list-head_start = 1.
it_packing_list-head_num = 0.
it_packing_list-body_start = 1.
describe table lt_mailtxt lines it_packing_list-body_num.
it_packing_list-doc_type = 'RAW'.
append it_packing_list.
CLEAR it_receivers.
it_receivers-receiver = email.
it_receivers-rec_type = 'U'.
it_receivers-com_type = 'INT'.
it_receivers-notif_del = 'X'.
it_receivers-notif_ndel = 'X'.
append it_receivers.
call function 'SO_DOCUMENT_SEND_API1'
       exporting
            document_data              = gd_doc_data
            put_in_outbox              = 'X'
            sender_address             = 'peykan.samli@****.com'
            sender_address_type        = 'INT'
            commit_work                = 'X'
       importing
            sent_to_all                = gd_sent_all
       tables
            packing_list               = it_packing_list
            contents_txt               = lt_mailtxt[] "it_message
            receivers                  = it_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.
IF sy-subrc EQ 0.
COMMIT WORK.
Push mail out from SAP outbox.
SUBMIT rsconn01 WITH mode = 'INT' AND RETURN.
ENDIF.

VF11 wrongly created with RV Doc type and with not clear status.

Hi All
Issue: There are 2 billing documents which were created(VF01) in March are canceled (VF11) in May. Cancel document is saved with a message (No automatic clearing of billing document XXXXXXXXX) and message diagnosis saying that u201CThe Automatic clearing of billing document and reversal is not possible. This may be, for example, because the line item update is deactivatedu201D
In the SD document flow cancel billing document is created and it's posted to accounting with Document type RV(which is not configured in the billing types) and it is in not clear status.
2 Sales order types are ZNRC(No Rebate u2013 Credit)    second is ZCR (CM Req With Refer).
Order Type : ZNRC , Billing type :ZG2, Cancel billing type :Z5, Accounting document in billing type for ZG2: is DG and accounting document in cancel billing type Z5 is :(_) blank.
Order type: ZCR Billing type :G2, Cancel billing type :S2, Accounting document in billing type for G2: is DG and accounting document in cancel billing type S2 is :(_) blank.
      FI document type Not maintained in the cancel billing type configuration because this should be determine by reversal document type DA which is maintained in DG document type from FI side. It will be triggered in VF11)
The above configuration is working with the order created VA01,billing VF01 and cancelling VF11 done in same period. If the order and billing done in old period and canceling(VF11) done in current period than FI document creating with RV document type and with not clear status in the document flow.
I reviewed similar issues with SAP Note and with below explanation:
          "There are 2 procedures that are possible when Vf11 is posted.
          Old Procedure - An FI "Reversal" document was created that was not connected with the orignal.
          New Procedure - A Real FI reversal was carried out with clearing."
In this case, our system is following with new procedure except above mentioned orders created in previous period and and canceled in current period.
My Questions are: How the RV document is getting triggered here? why the cancel document (Reversal FI Doc) is not clearing?
     Appreciate your answers or suggestions.
Thanks in advance,
Sunil
Edited by: Sunil kumar Matta on Jun 9, 2011 3:40 PM

Thank you Ivano.
I referred SAP note 1259505 and 339928. But initially we thought of none of the symptoms mentioned in the SAP note are matching with our issue. Then we contacted SAP online support and they suggested checking one SAP note (Mentioned above).
Our system is following new cancellation procedure, but itu2019s failing only for some few documents.
Finally we identified several reasons for the issue. One is profitability segment in the billing document and cancelled document is different due to some changes in segment assignments. Another one is consolidation- consolidation document does not exist in the billing document list but it is getting created in Canceled document (VF11).(Consolidation postings are switched off some time back and now itu2019s on)
After some discussions it is decided to include accounting document type (Reversal) in cancel billing types to avoid default RV document type in canceled billing document accounting document. And non-cleared documents need to be created manually in F-32.
Thread is closed.
Sunil

Service Entry sheet to be set as Not accepted status

Hi
After flagging the Transfer check box in the Settlement Tab in item details of shipment cost document(VI03), the Purchase order(ME23N) and Service entry sheet(ML81N) are automatically getting generated. PO and Service entry sheet numbers can be seen in Service Procurement tab.
Question 1: When I separetely look into PO, I am unable trace back the flow. I mean, there is no reference of Shipment cost number in PO.
Question 2: I want the service entry sheet to get on hold/not accepted status so that i can add the list of services performed by the Forwarding agent / service agent mentioned in Shipment cost document.
Question 3: I have made Release strategy for Service entry sheet which is properly working when i am accepting the entry sheet manually. But it is not working when the shipment cost document is triggering PO and Service entry sheet automatically. Actually, It should hold the service entry sheet from not being accepted.
Note: This subject is a mix of Transportation (Logistics Execution) and External Service Management (Materials management). The moderator of this forum can take a call on placement of this thread under suitable section.
Thanks
Maruthi Ram
Edited by: MARUTHI RAM on May 26, 2009 9:31 PM
Edited by: MARUTHI RAM on Jun 4, 2009 2:50 AM
Edited by: MARUTHI RAM on Jun 5, 2009 8:29 PM

not solved.

XI IDoc Acknowledgement - Acknowledgement not possible status

Hi Experts,
My scenario:
SAP IDOC - XI - jdbc (oracle)
Problem:
Getting the infamous "Acknowledgement not possible" status in SXI_MONI. I only need the transport acknowledgements back to SAP not the application acknowledgements. The messages themselves route fine from source to destination.

check if this blog helps you:
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
From the blog:
The system acknowledgement sent by the file adapter is converted into an ALE audit message and sent
back to the sender SAP system by an IDOC ACK channel configured in XI(an IDOC receiver adapter).
For your info:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb
Edited by: abhishek salvi on May 15, 2009 10:48 AM

Data objects in a Unicode program are not convertible?what does this mean?

hello,everyone,
when I execute a smartform directly in the transaction smartforms.,the result can be seen just no data.
when I execute program to transfer two internal tables from interface with data to the smartforms,and I use tcode st22,
the error is : Data objects in a Unicode program are not convertible.
the error analysis; The statement
"MOVE src TO dst"
requires the operands "dst" and "src" to be comvertible.
the source code that error occurs is :LOOP AT I_SHIP_DETAIL INTO WA_DETAIL .
and I know that the internal table have errors ,I defined the internal table refer to a structure created myself,and I set break-point in the smartforms ,can see the data in the internal table ,so why occurs such errors ,pls help me if you know .thank you in advance.

hi
good
go through this link
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f2dac69e-0e01-0010-e2b6-81c1e8e5ce50
thanks
mrutyun^

Few CRs are coimng under "Not Completed" status in CRM_DNO_MONITOR transact

Hi All,
Few (only 3) change requests are coming in "Not Completed" status in CRM_DNO_MONITOR transaction. Ideally all closed change requests should not come under "Not Completed" staus when reporting is done.
Kindly help.

Hi,
Please try to implement this note
1459839 CRM_SOCM_SERVICE_REPORT: no update on CRMD_ORDER wo
if after this still issue persists, then please run
CRM_INDEX_REBUILD to correct the CR's status
Hope this helps.
Cheers
SH

Error Message : Object does not exist (status management)

Hi Gurus,
I am working on tcode IW52(Change Notifications). and using badi's for validations at different points.
1. Order level,
2. Notification,
3. Task level validations.
In the task level validations, I have an requirement that if certain condition is met, than user should not be able to delete the task. I have no problem doing that, I am able to restrict it.
Now the issue is :
Say you have 6 tasks, and condition is met for the 5th task and I try to delete it. then the error message "can not delete task" is getting triggered from the badi.
and after this error message if you try to do any functionality on the 6th task, I am experiencing error message "Object does not exist (status management)".
Is anyone aware of this error message, any suggestions are highly appreciated.
Thanks in advance.
Shrikant
Edited by: Alvaro Tejada Galindo on Mar 17, 2008 1:56 PM

Hi ,
You have posted this question long back that is one and half year back nearly.
You got an error message in IW52 stating Object does not exist ( status management ).
Now iam also facing the same problem in iw22 transaction. Can you say me how you solved if you remember.

Unicode type not convertible

Hi,
Need some help in modifying the code ... I am working on a mass download of data into a texr file from the tables. Few of these tables have fields in decimal or currency and I need to read them into character string. I know the structure of the internal table I read the data into has to exactly match the table structure in Unicode environment. How to add that in the code when I am pulling the tables dynamically and reading their data in a sequential manner. Hence I am getting the above error.
Data: begin of i_list occurs 0,
      i_tabledata(2550) type c,
     end of i_list.
select * from (v_tabname) into i_list.   -
> Unicode type not convertible error...
        append i_list.
        clear i_list.
      endselect.
The value of 'v_tabname' comes from the table DD02l dynamically.
Any thoughts?
Thanks,
VG

As per your requirement, i developed this code snippet.
I download the data from ZTESTVBAK & upload the data to YTESTVBAK. Not sure why you're transferring the data to string & trying to read the string ?
Check this code snippet:
PARAMETERS: p_tab TYPE tabname OBLIGATORY DEFAULT 'ZTESTVBAK',
            p_dwld RADIOBUTTON GROUP grp1 DEFAULT 'X',
            p_upld RADIOBUTTON GROUP grp1.
DATA: dref TYPE REF TO data,
      v_tab TYPE tabname,
      lcx_sql_err TYPE REF TO cx_sy_sql_error,
      v_errtxt TYPE string.
FIELD-SYMBOLS: <itab> TYPE STANDARD TABLE,
               <wa> TYPE ANY.
CREATE DATA dref TYPE STANDARD TABLE OF (p_tab).
ASSIGN dref->* TO <itab>.
IF p_dwld = 'X'.
SELECT * FROM (p_tab) INTO TABLE <itab> UP TO 100 ROWS.
IF sy-subrc = 0.
    CALL FUNCTION 'GUI_DOWNLOAD'
      EXPORTING
        filename                = 'C:\dyntab.txt'
        write_field_separator   = 'X'
        confirm_overwrite       = 'X'
      TABLES
        data_tab                = <itab>
      EXCEPTIONS
        file_write_error        = 1
        no_batch                = 2
        gui_refuse_filetransfer = 3
        invalid_type            = 4
        no_authority            = 5
        unknown_error           = 6
        header_not_allowed      = 7
        separator_not_allowed   = 8
        filesize_not_allowed    = 9
        header_too_long         = 10
        dp_error_create         = 11
        dp_error_send           = 12
        dp_error_write          = 13
        unknown_dp_error        = 14
        access_denied           = 15
        dp_out_of_memory        = 16
        disk_full               = 17
        dp_timeout              = 18
        file_not_found          = 19
        dataprovider_exception = 20
        control_flush_error     = 21
        OTHERS                  = 22.
    IF sy-subrc = 0.
      WRITE: / 'File download successful.'.
    ENDIF.
ENDIF.
ELSEIF p_upld = 'X'.
CALL FUNCTION 'GUI_UPLOAD'
    EXPORTING
      filename                = 'C:\dyntab.txt'
      has_field_separator     = 'X'
    TABLES
      data_tab                = <itab>
    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.
IF sy-subrc = 0.
    v_tab = p_tab.
*   Lock the table records
    CALL FUNCTION 'ENQUEUE_E_TABLEE'
      EXPORTING
        tabname        = v_tab
      EXCEPTIONS
        foreign_lock   = 1
        system_failure = 2
        OTHERS         = 3.
    IF sy-subrc = 0.
      TRY .
          MODIFY (p_tab) FROM TABLE <itab>.
        CATCH cx_sy_sql_error INTO lcx_sql_err.
          v_errtxt = lcx_sql_err->get_text( ).
      ENDTRY.
    ENDIF.
*   Unlock the table records
    CALL FUNCTION 'DEQUEUE_E_TABLE'
      EXPORTING
        tabname = v_tab.
    COMMIT WORK.
ENDIF.
ENDIF.
Hope this helps.
BR,
Suhas

IDOC Error - Entry in outbound table not found - Status 37

Hello,
we try to generate the IDOC in a Test Tool WE19. I always get the same error "Entry in outbound table not found" - Status 37. I tried already many config changes (Partner, Ports, Distribution Modell...).
The thing is that the IDOC should be sent on external system (non-SAP System) but also the IDOC should be write to file. The external system should later on catch the IDOC and process the data.
I suppose the problem is the fact that we send it to external non-SAP System. I add as Port Data and the source where the IDOC shoud be generated. The Partner that I choose is logical system. However I dont specify the RFC Connection because the file should only be saved and not send directly on the external system. Is it possible or maybe I need to specify the IP-Adress of the external system?
When it works I need to generate the IDOC as service management IW32. I try it with TA IORD. I get the message "rejected". Probably because of the error in the test tool WE19.
I am already fighting on it for many hours...
Thank you in advance
Michael

Hi
In we 19
Receiver
Port: A port created in R/3 referencing RFC dest pointing to XI.
Partner no: LS of XI (CLNT100)
Partner Type: LS
Sender
Partner no: LS of R/3 (RD1CLNT500)
Partner Type: LS
Message Type is DESADV
Basic DELVRY05
and i am sending blank idoc for testing.
Regards
Monika

How do i test a record containing status E0008 and not containing status I0002

hello all,
how do i test a record containing status E0008 and not containing status I0002 for a given WBS Element....
the data(like pspnr, posid and objnr from table PRPS are avialable in internal table it_prps)....

Hi,
You can check the received table from the function module as per your condition.
loop at it_prps.
     call function STATUS_READ and pass objnr
          "suppose tables parameter data is in table itab
     Read table itab with key STAT = 'E0008'. "check for E0008
       if sy-subrc = 0.
          read table itab with key stat = 'I0002'. "if E0008 exists then check for I0002
               if sy-subrc = 0.
                   "both status E0008 & I0002 exists so delete this record from it_prps
                    delete it_prps.
               else.
                   "only status E0008 exists.
               endif.
     endif.

Employee replications stuck in 'Not started' status.

Some of the Employee replication has been stuck in not started status.When you go to the edit mode and click on replicate and then save, the entries will be saved. But the status of the employee replication will be in not started status instead of successful or failed status.
The reason might be discrepancy in the secondary persistence. This lead to the fact that you got records by the query which seemed to be relevant, but in the original persistence they were already marked as irrelevant. From SAP end we trigger a reload of the secondary persistence and the issue will be solved.
Thanks.
Cryssal

Do you think there is an agent logged in and Not Ready, or do you think it's a hung session?
If you think it's a real login, reboot the PC.
If you think it's a hung session then you'll have to restart a service of two. I would just plan for a maintenance window and reboot the server along with your CUCM CTI Manager.
Good luck and happy troubleshooting!
Sent from Cisco Technical Support iPhone App

Error in ME21n 'The date 1,245 is not convertible (pl correct).

While preparing a STO thru T.Code ME21N , system is giving an error 'The date 1,245 is not convertible (pl correct).
Can u pl help us in analysing why the error is coming.
Regards,
Paras

Hi
Enter the date format as per user prifile sysem config.
Check In SU3 T-code deafult tab-date format
Like example MMDDYYYY/DDMMYYYY/YYYYMMDD
Nagaraj K

The date 00.00.0000 is not convertible (please correct)

Hi,
While creating Production order through CO01 system is showing the error message
The date 00.00.0000 is not convertible (please correct)
Message no. 61060
At the time release only system showing this error message.
Regards,
Teja

y
Edited by: M Madhu on Mar 11, 2010 4:01 PM

PReq 1100000000/ not convertible (status )

Similar Messages

Maybe you are looking for