Add segment in Idocs Error Idocs Document date 00.00.0000 is incorrect in item

Hi every body ,
I have the idocs WMMBXY with error <Document date 00.00.0000 is incorrect in item >
because one segment is missing E1MBXYH in this idocs
How can i add this segment <E1MBXYH > to process my idocs
Thank you

Thank you for your feedback
Now i have add the segment E1MBXYH and the date wich was missing , i prossec l'idoc in forground , and i have an other error <<Please check table 158 : entry WE19 does not exist>>
here the screen shot , did you know how i can solve this ??.

Similar Messages

Error F5 833 Document date 00/00/0000 is incorrect in item 000000000

Hi SD Gurus,
An invoice with reference to sales order has been created without an accounting document. An error "Message no. F5 833 Document date 00/00/0000 is incorrect in item 000000000" pops when I release document to accounting.
Any idea why it is giving this error?
Best regards,
Rose Sioson
SD

Hi,
Check the following -
1. In sales order, is systerm determined Document date at header level, billing date at header and item level
2. Is your copy control settings are maintained properly between sales order to billing
3. In copy controls header, activate Copy item number
4. In the VTFL transaction, check wether item increment number is blank
5. Check in billing document before saving, is system determining the billing date both at header and item level.
Regards
Goutham

LSMW IDoc error : APPLICATION DOCUMENT NOT POSTED with error 51

During LSMW matmas04 uploading i m getting error :APPLICATION DOCUMENT NOT POSTED with error 51
Can some one tell why ots coming so.

to check errors check We05 or we02 they are same
in general i think that most of problem is relate to Dates if that your case check that you converted dates to internal format using conversion step i advice use like this function
CALL FUNCTION 'CONVERT_DATE_TO_INTERNAL'
EXPORTING
DATE_EXTERNAL = ZHEADER-BEDAT
IMPORTING
DATE_INTERNAL = MBEPOH-BEDAT.
<Removed by Moderator>
Message was edited by: Marcelo Ramos

IDoc Error IDocs showing the status 53 "Application Document Posted".

Hi All
IDocs showing the status 53 "Application Document Posted". But values are not updated in SAP.
Plaese sugggest on this,
Thanks
Ajit K Barik

Ajit, there might have been a dump--check in ST22 or a update termination error, check in SM13.
Either of these you'll have to take help of your ABAP consultant to analyse.
Regards,
Raghu.

Idoc error: Application document not posted

Hi expert,
I hope we can halp me urgently!
I'm load data from CRM 7.1 system to my BW 7.0 system, but the request goes in error for timeout.
The problem is caused by an IDOC whose text error is following:
Target system BWDCLNT100 is not known in the source system.
Idoc current status --> 51
I already check the rfc connection bytcode SM59 and are ok.
I believe that some IDOC settings missing. But where and How?
Thanks for your answers.
Claudia

can you check the RFC connections in SM59 / also check background users authorizations were changed ?
Also Check WE05/WE20 tcode and If any IDOCS are stucked there you can execute them thru BD87

Where can get IDOC Error Message from Data base tables

Hi ,
i am automating idoc checking process,in which i am getting control record from EDIDC tables,now i need to fetch Error message
using this idoc no.
How can fetch error message text ?
Thanks in advance.
Regards
sarath

Hi its a structure, it doesnt store data.
Take it from the table specified,
Pass STAMID,STAMNO,STAPA1,STAPA2,STAPA3,STAPA4 to function module MESSAGE_PREPARE and you will get the message text.
Also check the function module IDOC_READ_COMPLETELY

LSMW-IDOC error while tranferring data from ECC to CRM

Hi,
We got an error
Error status 'A' calling validation service.
Validation error occured: "Module CRM_BUPA_MAIN_VAL, B Doc type BUPA_MAI".
When we are doing LSMW with IDOC in CRM.
Please provide ur valuable help in this problem.
Thanks & Regards
Sriram Tumuluri

Amar,
please check the source system job status. If its successfully completed then we can expect data load sucess in BW side.
to check source system status: RSMO> select related load>in Menu Environment-->Job overview in source system.
once this over check the TRFC or IDocs struck
if TRFC, chk in TCode-SM58 or from environment select TRFC from source/data warhouse.
if you are finding TRFcs are in stuck just select and run manually to complete.
M

IDOC Error Follow-up Date

Kindly advise how to overcome / (Follow-up Date)
error in IDOC inbound process ,however we are unable to reprocess this IDOC .. In what case this type of problems will come ... kindly reveal me about this error.
Thanks With Regards

Use transaction WE19 to edit data i Idoc and try posting it. You should filll all mandatory fields of Idoc.
Could you also tell us which Idoc are u using.
Cheers
Ankur

Error in document date & posting date-- Posting period 001 2008 is not open

hi guru's
while doing vendor creation in XK01, i m not getting the data screens like address, ..etc.i m getting error..posting period not open". what does it mean..
What date i need to give in both fields...?
can anybody send a set of data for me to create a vendor to test for my bdc/lsmw?
can any help me step by step vendor creation in xk01,
I am getting this below....
Posting period 001 2008 is not open
Message no. F5201
Diagnosis
Period 001 of fiscal year 2008 is not open for posting for the variant of posting period 1000.
System Response
Processing cannot be continued.
Procedure
The error can have several causes. In order to eliminate the error, proceed as follows:
1. Check whether the posting date was entered correctly. The system determines the posting period by means of the date.
2. Check whether the required posting period is open for posting for the variant of posting period 1000 and account type +. Make sure that the period is open for posting.
To do this, specify a period interval in which the required period for the variant of posting period 1000 and account type + is contained.
Proceed
thanks

Hi
Kris is right, that message means you can't post a FI document in the period 1 (probably Gennuary) of the 2008, but this can't mean you can't create a new vendor.
So are you sure on trx?
If the trx is right perhaps somebody has inserted a control in a user-exit.
Max

Error in document date and posting date

hi guru's
while doing vendor creation in XK01, i m not getting the data screens like address, ..etc.i m getting error..posting period not open". what does it mean..
What date i need to give in both fields...?
can anybody send a set of data for me to create a vendor to test for my bdc/lsmw?
can any help me step by step vendor creation in xk01,
I am getting this below....
Posting period 001 2008 is not open
Message no. F5201
Diagnosis
Period 001 of fiscal year 2008 is not open for posting for the variant of posting period 1000.
System Response
Processing cannot be continued.
Procedure
The error can have several causes. In order to eliminate the error, proceed as follows:
1. Check whether the posting date was entered correctly. The system determines the posting period by means of the date.
2. Check whether the required posting period is open for posting for the variant of posting period 1000 and account type +. Make sure that the period is open for posting.
To do this, specify a period interval in which the required period for the variant of posting period 1000 and account type + is contained.
Proceed
thanks
Edited by: Raji on Jan 23, 2008 8:21 AM
Edited by: Raji on Jan 23, 2008 8:37 AM

Goto
T.code: OB52...open the posting period for your posting period variant...
Regards
s.Baskaran

IDoc Error 51 - Make Entry in All Required Fields

hi,
I am using a scenario where an idoc is being posted into an R/3 system from a legacy application. For some reason I keep getting Idoc error 51 (Document not posted).
Once I drill down further, the specific error states "Make entry in all required fields". Have checked to make sure all mandatory fields have been mapped and proper constant values have been specified.
But cannot seem to get rid of the problem. Could anybody help out in determining how else to troubleshoot this and identify the possible cause?
thx,
Manpreet

Manpreet,
What IDoc Type you are trying to post ? One way is debugging the inbound function module using WE19. The second option is talking to a functional consultantor who worked, what fields are needed for that particular IDoc.
I wouldn't care much about whether the IDoc is posted or not because, it is the ABAP ALE/EDI consultant's job to do that. The only way XI Developer is concerned is when it is not posting, ABAPer would tell what's missing.
Hope this info helps.
regards
SKM

Regarding : Material document data and PO data do not match (Plant)

Hi Gurus,
Please go through this BAPI program.
While uploading it is giving an error ' Material document data and PO data do not match (Plant) '.
Please help regarding this issue.For all Other moment types it is working fine except this 351 moment type.
dATA: i_excel TYPE truxs_t_text_data. "work table for excel upload
DATA: BEGIN OF it_itab OCCURS 100,
      docdate(10),
      postdate(10),
      mvt_type(3), "Movement Type
      plant(4), "Plant
      lgort(4),
      pur_doc(10), "Purchase Document No
      po_item(3), "Purchase Document Item No
      material(18), "Material Number
     delnote(16),
      erfmg(13),
      uom(3),
     lfmng(13), "Quantity
      batch(10) TYPE c,
      vfdat TYPE vfdat,
      END OF it_itab.
DATA: it_goodsmvt_head TYPE TABLE OF bapi2017_gm_head_01      INITIAL SIZE 100,
      it_goodsmvt_code TYPE TABLE OF bapi2017_gm_code         INITIAL SIZE 100,
      it_goodsmvt_item TYPE TABLE OF bapi2017_gm_item_create INITIAL SIZE 100.
DATA: wa_goodsmvt_head LIKE LINE OF it_goodsmvt_head,
      wa_goodsmvt_code LIKE LINE OF it_goodsmvt_code,
      wa_goodsmvt_item LIKE LINE OF it_goodsmvt_item.
DATA: w_mat_doc TYPE bapi2017_gm_head_ret-mat_doc,
      w_year     TYPE bapi2017_gm_head_ret-doc_year.
DATA: BEGIN OF it_errmsg_goodsmvt OCCURS 10.
        INCLUDE STRUCTURE bapiret2.
DATA: END OF it_errmsg_goodsmvt.
DATA : obj_type LIKE bapiache09-obj_type,
       obj_key LIKE bapiache09-obj_key,
       obj_sys LIKE bapiache09-obj_sys.
DATA: v_date1 TYPE sy-datum.
DATA: v_date2 TYPE sy-datum.
DATA: w_lines TYPE i.
DATA: errflag.
SELECTION-SCREEN BEGIN OF BLOCK bk1 WITH FRAME TITLE text-100.
PARAMETERS: p_file TYPE rlgrap-filename.
SELECTION-SCREEN END OF BLOCK bk1.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
CALL FUNCTION 'F4_FILENAME'
    EXPORTING
      field_name = 'P_FILE'
    IMPORTING
      file_name = p_file.
Start-of-selection processing
START-OF-SELECTION.
CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
    EXPORTING
      i_line_header        = 'X'
      i_tab_raw_data       = i_excel
      i_filename           = p_file
    TABLES
      i_tab_converted_data = it_itab[]
    EXCEPTIONS
      conversion_failed    = 1
      OTHERS               = 2.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
LOOP AT it_itab.
    REFRESH it_goodsmvt_head.
    REFRESH it_goodsmvt_item.
    CONCATENATE it_itab-docdate6(4) it_itab-docdate3(2) it_itab-docdate+0(2) INTO v_date1.
    CONCATENATE it_itab-postdate6(4) it_itab-postdate3(2) it_itab-postdate+0(2) INTO v_date2.
    wa_goodsmvt_head-pstng_date = v_date2.
    wa_goodsmvt_head-doc_date   = v_date1.
   wa_goodsmvt_head-ref_doc_no = it_itab-delnote.
wa_goodsmvt_head-pr_uname   = sy-uname.
    APPEND wa_goodsmvt_head TO it_goodsmvt_head.
Maintain it_goodsmvt_code
    wa_goodsmvt_code-gm_code    = '04'.
Maintain it_goodsmvt_item
*LOOP AT it_itab.
IF wa_goodsmvt_item-po_number IS INITIAL.
    wa_goodsmvt_item-po_number    = it_itab-pur_doc.
    wa_goodsmvt_item-move_type    = it_itab-mvt_type.
    wa_goodsmvt_item-MOVE_PLANT      = it_itab-plant.
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
      EXPORTING
        input = it_itab-material
      IMPORTING
        output = it_itab-material.
    wa_goodsmvt_item-material     = it_itab-material.
    wa_goodsmvt_item-stge_loc     = it_itab-lgort.
    wa_goodsmvt_item-po_item      = it_itab-po_item.
    wa_goodsmvt_item-entry_qnt    = it_itab-erfmg.
    wa_goodsmvt_item-ENTRY_UOM_ISO    = it_itab-uom.
   wa_goodsmvt_item-po_pr_qnt    = it_itab-lfmng.
    wa_goodsmvt_item-batch        = it_itab-batch.
    wa_goodsmvt_item-expirydate   = it_itab-vfdat.
   wa_goodsmvt_item-NO_MORE_GR   = 'X'.
    wa_goodsmvt_item-mvt_ind      = 'B'.
    APPEND wa_goodsmvt_item TO it_goodsmvt_item.
    CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
      EXPORTING
        goodsmvt_header = wa_goodsmvt_head
        goodsmvt_code    = wa_goodsmvt_code
      IMPORTING
        materialdocument = w_mat_doc
      TABLES
        goodsmvt_item    = it_goodsmvt_item
        return           = it_errmsg_goodsmvt.
Process of commit work
    IF it_goodsmvt_head[] IS NOT INITIAL.
      DESCRIBE TABLE it_goodsmvt_head LINES w_lines.
    ENDIF.
    IF it_goodsmvt_item[] IS NOT INITIAL.
      DESCRIBE TABLE it_goodsmvt_item LINES w_lines.
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
        EXPORTING
          wait = 'X'.
    IMPORTING
    RETURN        =
      CLEAR errflag.
      READ TABLE it_errmsg_goodsmvt INDEX 1.
      IF it_errmsg_goodsmvt-type EQ 'E'.
        WRITE:/'Error in function', it_errmsg_goodsmvt-message.
        errflag = 'X'.
      ELSE.
        WRITE:/ it_errmsg_goodsmvt-message.
      ENDIF.
      IF errflag IS INITIAL.
        COMMIT WORK AND WAIT.
        IF sy-subrc NE 0.
          WRITE:/ 'Error in updating'.
          EXIT.
        ELSE.
          WRITE:/ 'Material Document created successfully and the Document Number for the Material',
                  wa_goodsmvt_item-material,'is:', w_mat_doc, w_year.
        ENDIF.
      ENDIF.
    ENDIF.
ENDLOOP.

Hey,
Just wanted to post that in my case this was the error of MVT_IND field in item table. When I made it from 'B' to blank then it worked.
Mine is solved....
Thanks

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

Error : IDoc XML data record: In segment attribute occurred instead of SEGM

hi friends
i am doing the file to idoc scenario. in message mapping i had done the static test. but what ever the fields i mapped in the idoc it was not populated in the idoc. and i am getting the error as
error :IDoc XML data record: In segment attribute occurred instead of SEGMENT
can any one solve the problem please
thanks in advance
Vasu

Hi Vasudeva,
Pls do check the nodes which you have mapped to. Also make sure that your SEGMENT field in the target structure is mapped properly.
Cheers
JK

Error : idoc xml data record : in segment attribute instead of SEGMENT

hi all
i am doing the file to idoc scenario. in that i am getting the error
error : IDOC XML Data record : In segment attribute instead of SEGMENT
i am doing this scenario since 4 days.
can anyone help me
thanks a lot
Vasu

in ref. to my post in your earlier thread.
>>>>
in your mapping check, in your IDOC if Begin , segment etc are mapped to a constant say '1'.
Also ref: In segment IDOC attribute I occurred instead of SEGMENT

Add segment in Idocs Error Idocs Document date 00.00.0000 is incorrect in item

Similar Messages

Maybe you are looking for