Idoc Error - EDI: Syntax error in IDoc (segment cannot be identified)

Hi All,
have created a new reduced message type for our new vendor A/C group through BD53. Also done reqd config for sending the vendor master through this message type. .
I have created couple of vendors for testing with X01 with withholding tax functionality and when try to send these vendors , Idocs are getting failed .
When I create vendor without withholding tax functionality , idoc is getting posted succesfully . If create vendor with entries in the feild whih are related to withholding tax . Idocs are getting failed .
If I see the status in WE05 ,Idocs which are posted succefully are showing the basic type as CREMAS03 . For idocs which are getting failed have the basic type as CREMAS04 and also the extension as Z1CREMAS . I don`t understand why the system is defaulting CREMA04 & Z1CREMAS when I send the vendor master with withholding tax feild entries.
I am not much familiar with ALE /Idoc set up. Please can any body help me to resolve the issue.
The error message in we05 as below
EDI: Syntax error in IDoc (segment cannot be identified)
Message no. E0078
Diagnosis
The segment Z1LFA1M does not occur at the current level of the basic type CREMAS04 (extension Z1CREMAS).
This error can have several reasons:
The segment Z1LFA1M is assigned to a group whose header segment does not occur.
The segment Z1LFA1M does not exist in the syntax description of the basic type CREMAS04 (extension Z1CREMAS).
The sequence of segments in the group in which the segment appears is incorrect.
Previous errors ('mandatory' segment or group missing) may be due to this error.
Procedure
Please check the IDoc or the syntax description of the basic type CREMAS04 (extension Z1CREMAS).
Thanks

Hi,
I don`t understand what do you mean release after adding segment.
Message type works i.e. Idoc get posted if I send with the vendor w/o withholding tax field entries. Idoc fails when send vendor with withholding tax field entry.
Regards

Similar Messages

EDI: Syntax error in IDoc (segment cannot be identified)

Hi All,
Im facing the below error EDI: Syntax error in IDoc (segment cannot be identified).
And this error is coming only for few idocs rest are getting processed successfully.
Message no. E0078
Diagnosis
The segment E1EDP03 does not occur at the current level of the basic type ORDERS05 (extension ).
This error can have several reasons:
The segment E1EDP03 is assigned to a group whose header segment does not occur.
The segment E1EDP03 does not exist in the syntax description of the basic type ORDERS05 (extension ).
The sequence of segments in the group in which the segment appears is incorrect.
Previous errors ('mandatory' segment or group missing) may be due to this error.
Procedure
Please check the IDoc or the syntax description of the basic type ORDERS05 (extension ).
Please suugest.
Thanks,
Spandana

Hi,
Is this standard program or custom program?
you might be appending the Z segment instead of inserting it. Always best practice is get the index of the segment and instert it.
If all the data is not populated then segment position will change incase of appending. Please check your code and revert back.
Refer the below link for detailed information.
IDOC Status 26: EDI: Syntax error in IDoc (segment cannot be identified).
Thank you

Error during syntax check of IDoc (outbound)

Hello,
I did an insert into idoc_data of segment E1TXTH8 (level 3 - as child of E1EDL20) and E1TXTP8 (level 4 as child of E1TXTH8).
inside user-exit ZXTRKU02.
But idoc is created with error 26 (and hierarchy is not respected! (WE05)).
Am I using the right user-exit or i miss something in the sequence while insert??
Error:
EDI: Syntax error in IDoc (segment cannot be identified)
Message no. E0078
Diagnosis
The segment E1TXTH8 does not occur at the current level of the basic type DELVRY03 (extension ).
This error can have several reasons:
The segment E1TXTH8 is assigned to a group whose header segment does not occur.
The segment E1TXTH8 does not exist in the syntax description of the basic type DELVRY03 (extension ).
The sequence of segments in the group in which the segment appears is incorrect.
Previous errors ('mandatory' segment or group missing) may be due to this error.
Procedure
Please check the IDoc or the syntax description of the basic type DELVRY03 (extension ).
Thank you in advance for your help.
Edited by: Fakher Baklouti on Apr 9, 2010 7:12 PM

Hello Faker,
It depends on the previous available segment.
Here is the procedure,
1. Get all the segments from the database table IDOCSYN where basic type is DELVRY03
2. Sort them by Sequential number in DESCENDING
3. Get the Index (say GV_INDEX) of the segment in IDOCSYN which you want to insert or edit
4. LOOP internal table of IDOCSYN from index GV_INDEX and check for the availability of the segment of IDOCSYN in idoc data
5. If it is success, break the loop and now you got the previous available segment
6. Now just insert your segment in the idoc table just after it.

IDOC Status 26: EDI: Syntax error in IDoc (segment cannot be identified).

Hi All,
I have created IDOC extension for IDOC Basic type "PROACT01" and have followed all required necessary steps but getting IDOC
Status 26. EDI: Syntax error in IDoc (segment cannot be identified). The exact error is:
Please check Error Details and the details of the steps I followed for Setting up IDOC Extension:
Error Detail :
EDI: Syntax error in IDoc (segment cannot be identified)
Message no. E0078
Diagnosis
The segment ZPROSEG does not occur at the current level of the basic type PROACT01 (extension PROACTEX).
This error can have several reasons:
The segment ZPROSEG is assigned to a group whose header segment does not occur.
The segment ZPROSEG does not exist in the syntax description of the basic type PROACT01 (extension PROACTEX).
The sequence of segments in the group in which the segment appears is incorrect.
Previous errors ('mandatory' segment or group missing) may be due to this error.
Procedure
Please check the IDoc or the syntax description of the basic type PROACT01 (extension PROACTEX).
Can you please look at this problem and suggest what is wrong with IDOC Extension/Custome Segment?
Below is the Details of the Steps which I have followed:
1. Tcode WE31 - Created new custom Segment ZPROSEG with 4 fields. Released segment.
2. TCode WE30 - Created IDOC Extension PROACTEX for Basic Type PROACT01. Released IDOC extension.
Here when I run syntax check warning appears "No predecessors exist". I am not sure if its okay!!
3. TCode WE82 - Added Extension PROACTEX in the Message Type PROACT with BASIC Type PROACT01.
4. TCode WE20 - Added IDOC Extension PROACTEX in the predefined partner profile in WE20 transaction.
5. Added the following code in the Customer Exit EXIT_SAPLWVMI_001 include ZXWVMIU01 .
DATA segnam(27).
READ TABLE dedidd WITH KEY segnam = 'ZPROSEG'.
IF sy-subrc NE 0.
LOOP AT dedidd WHERE segnam = 'E1EDP31'.
CLEAR dedidd.
dedidd-segnam = 'ZPROSEG'.
zproseg-matnr = 'Mat1'.
zproseg-lgort = '001'.
zproseg-gernr = 'SNo1'.
zproseg-labst = 2.
dedidd-sdata = zproseg.
APPEND dedidd.
ENDLOOP.
ENDIF.
Finally ran transaction WVM2 (Transfer of Stock & Sales Data) to generate IDOC, its creating IDOC but when checked IDOC in WE05 its getting Status Error "26".
Looking forward for your reply.
Many thanks in advance.

Hello,
Actually you are appending the Z segment instead of inserting into the correct position. So the segment is added at the last, so hierarchy of segments is collapsed.
So get the index of the previous segment E1EDP31 and increase the index by 1 and INSERT the Z segment with that new index as below.
LOOP AT dedidd WHERE segnam = 'E1EDP31'.
lv_index = sy-tabix. " <<--
ADD 1 TO lv_index. " <<--
CLEAR dedidd.
dedidd-segnam = 'ZPROSEG'.
zproseg-matnr = 'Mat1'.
zproseg-lgort = '001'.
zproseg-gernr = 'SNo1'.
zproseg-labst = 2.
dedidd-sdata = zproseg.
*APPEND dedidd.
INSERT dedidd INDEX lv_index. " <<---
ENDLOOP.
Here actually we are insering the record inside the LOOP and it regenerates the index again. It is not actually a good practice.
So the best practice is get the index and generate the segment inside the loop, store them into another internal table, come out the loop and insert the Z segments into DEDIDD by looping the new internal table.

Issue:EDI: Syntax error in IDoc (mandatory segment missing):Idoc extention

Hi all,
I have extended the the standard IDOC MATMAS05 classification view with structure as below-
E1MARAM                        Master material general data (MARA)--->Mandatory segment
     Z1KLART                        KLART --->Extended chaild to E1MARAM
         Z1CLASS                        segment for class --->Extended chaild to Z1KLART
         Z1CHARACTERISTIC               CHARACTERISTIC --->Extended chaild to Z1KLART
     E1MARA1                        Additional Fields for E1MARAM
     E1MAKTM                        Master material short texts (MAKT) --->Mandatory segment(Child   to
E1MARAM )
I am getting an error in IDOC fro material master as:EDI: Syntax error in IDoc (mandatory segment missing ).
Diagnosys By system is :*The segment E1MAKTM has the attribute 'Mandatory' in the syntax description of the basic type MATMAS05 (customer enhancement ZMATMAS05). However, the segment is missing in the IDoc. The segment number logged in the status record identifies the item before which the segment is missing.
This error may have been triggered by an unidentifiable segment before the expected mandatory segment.*
Please help to resolve the issue.
Thank you.
Edited by: sanu debu on Apr 30, 2009 11:25 AM
Edited by: sanu debu on Apr 30, 2009 11:31 AM

Hi,
   You cannot add an segment in the middle of other segments.
YOu have to add any segment at the last.
If you want to add a segment as the child of another segment, it should be added after the last child of the parent segment.
In you case, you have to add your segment after the E1CUCFG segment.(NOt under that segement)
Regards,
Ravi Kanth Talagana

EDI: Syntax error in IDoc (mandatory group/segment missing)

hi EDI/IDoc experts,
Need you help urgently. According to the requirement, i need populate a segement E1IDT01 of basic type PEXR2002 . I added the code , then run and generate an idoc , the new segment
E1IDT01 was populated, but Syntax error 26 happend. Error message as below.   It also strange that i can see E1IDKU5 populate out as usual, but some others segment disappeared , i am sure that in my code ,i didn't changed any variable related to other segement . how can i fix this problem?
EDI: Syntax error in IDoc (mandatory group missing)
Message no. E0079
Diagnosis
The segment group E1IDKU5 has the attribute 'Mandatory' in the syntax description of the basic type PEXR2002 (customer enhancement ). However, the segment group is missing in the IDoc. The segment number logged in the status record identifies the item before which the segment group is missing.
Procedure
Please check the IDoc or the syntax description of the basic type PEXR2002 (customer enhancement ).

Hi all,
Thanks so much for your concern!
Finally ,this problem has been figured out .
Requirement is user want to use segment E1IDT01 in idoc to populate the long text they maintained in accounting document vendor item line (use FB01 to create accounting doc).
Why I made out " EDI: Syntax error in IDoc (mandatory group/segment missing)" this message out ,because I didn't fill data correctly. I missed to keep SY-TABIX in momory .
when we use Function module ,or do..enddo...or read table it_table. we should be careful that SY-TABIX is changed .So we can't just use MODIFY EDIDD_TABLE INDEX SY-TABIX in the last . we should define a local variable to keep SY-TABIX in memory and then use it to modify EDIDD_TABLE.
Follow is the final code.
IF SEGMENT_NAME = 'E1IDT01'.
TABLES :STXL.
* Define for long text getting
DATA: LIT_TLINE LIKE TLINE   OCCURS 0 WITH HEADER LINE.
DATA: LV_STRING(2000) TYPE C.
DATA: LV_TDNAME TYPE THEAD-TDNAME,
        LV_ID     TYPE THEAD-TDID     VALUE '0001',
        LV_LANG   TYPE THEAD-TDSPRAS VALUE 'E' ,
        LV_OBJ    TYPE THEAD-TDOBJECT VALUE 'DOC_ITEM'.
data:   LV_LINE   TYPE I,                " long Text lines
        LV_LEN    TYPE I,                " long Text length
        LV_TABIX LIKE SY-TABIX.
* Clear memory
CLEAR:LV_TDNAME,
        LV_STRING,
        LV_LINE,
        LIT_TLINE, LIT_TLINE[],
        LV_LEN,
        LV_TABIX.
* Keep sy-tabix memory using a variable--This is the key point
LV_TABIX = SY-TABIX.
* Combine TDNAME with company code + accounting doc + fiscal year + item number.
    CONCATENATE REGUP_DATA-BUKRS REGUP_DATA-BELNR
                 REGUP_DATA-GJAHR REGUP_DATA-BUZEI INTO LV_TDNAME.
* When vendor item has long text , read long text into lv_string
    SELECT SINGLE *
      FROM STXL
      WHERE TDOBJECT = LV_OBJ
        AND TDNAME   = LV_TDNAME
        AND TDID     = LV_ID
        AND TDSPRAS = 'E'.
    IF SY-SUBRC = 0.
      CALL FUNCTION 'READ_TEXT'
        EXPORTING
          CLIENT   = SY-MANDT
          ID       = LV_ID
          LANGUAGE = LV_LANG
          NAME     = LV_TDNAME
          OBJECT   = LV_OBJ
        TABLES
          LINES    = LIT_TLINE.
      IF NOT LIT_TLINE[] IS INITIAL.
        DESCRIBE TABLE LIT_TLINE LINES LV_LINE.
        DO LV_LINE TIMES.
          READ TABLE LIT_TLINE INDEX SY-INDEX.
          CONCATENATE LV_STRING LIT_TLINE-TDLINE INTO LV_STRING.
        ENDDO.
        LV_LEN = STRLEN( LV_STRING ).
* Make sure we only need less than 840 charicters
        IF LV_LEN > 840.
          LV_STRING = LV_STRING+0(840).
          LV_LEN    = 840.
        ENDIF.
* Populate Vendor item long text with segment E1IDT01 start from
* Fields TXT03 to TXT14.
         EDIDD_TABLE-SDATA+147(LV_LEN) = LV_STRING.
        MODIFY EDIDD_TABLE INDEX LV_TABIX.
      ENDIF.
    ENDIF.
ENDIF.

EDI: Syntax error in IDoc (mandatory segment missing)

HI all,
Error Message - EDI: Syntax error in IDoc (mandatory segment missing)
Status ID - E0
Message No - 072
Status of the IDoc - 26
Please help me how to solve this issue?
Thanks,
Srini

Hi,
This error normally comes up when the sequence of segments has been disturbed.
For successfully posting an IDOC you need to maintain the sequence of the segments as in WE30.
You can also check which segments are mandatory in WE30 by clicking on the segment name and the pop up that comes.
Thanks,
Manish

Regarding EDI: Syntax error in IDoc (segment cannot be identified)

Hi,
My requirement is that I was adding two diffrent field values under two diffrent segments as "E1EDKA1" and "E1EDK02" in outbound invoice IDOCS, INVOIC02 (process code: SD09 - IDOC_OUTPUT_INVOIC).
I am getting the IDOC number through Tcode "VF02". Can any body give me idea how to check that syntax error in debug mode.
Please find the following error details using TCODE "WE02".
*EDI: Syntax error in IDoc (segment cannot be identified)*
*Message no. E0 078*
*Diagnosis*
*The segment E1EDKA1 does not occur at the current level of the basic type INVOIC02 (extension ).*
*This error can have several reasons:*
*The segment E1EDKA1 is assigned to a group whose header segment does not occur.*
*The segment E1EDKA1 does not exist in the syntax description of the basic type INVOIC02 (extension ).*
*The sequence of segments in the group in which the segment appears is incorrect.*
*Previous errors ('mandatory' segment or group missing) may be due to this error.*
Please help me to resolve this problem. <REMOVED BY MODERATOR>
Regards,
Skumar.
Edited by: Alvaro Tejada Galindo on Apr 28, 2008 1:09 PM

It seems that you added segment E1EDKA1 at a place where it is not supposed to be. That's where this error is coming from. The structure of every IDOC is definded by SAP standard and you cannot change the sequence or the level of standard segments. If you require a certain field at a certain level you have to add that field to a Z-segment and then add that Z-segment where appropriate in your extension.
Hope that helps,
Michael

EDI: Syntax error in IDoc (too many repetitions of a segment)

Hi All -
We are getting an "EDI: Syntax error in IDoc (too many repetitions of a segment)" error message while processing the REMADV message in the payment run program.
Basic Type : PEXR2002
Message Type : REMADV
Segment Name : E1EDP02
This issue is due to BELNR length in above segment, since payment run program assigning the 45 chars but BELNR length is 35 char, is there any way or OSS notes we can implement to rectify the same.
Thanks in Advance.
Rds,
K

Hi,
This error is the segment definition violation. Open your BASIC IDOC type in WE30, double click on the segment TESTIDOC.
In the popup you can see properties like mandatory segment, Minimum number and Max number. Your IDOC is crossing the max number of repetitions it can have. If any of the segment definition perperties like this one, or improper position of the segment etc occurs IDOC is generated with syntax error.
Thanks,
Vinod.

Error 26: Error during syntax check of IDoc (outbound)

Hi all,
   I am getting error when we try to generate IDoc in Outbound process (to send data from SAP to external Interface).
Error no is 26. And I have checked the status records, it shows the below error message. "EDI: Syntax error in IDoc (too many repetitions of a group). According to the syntax description of the basic type SHPMNT05 (customer enhancement ZSHPMNT05), the segment group E1EDL37 can be repeated a maximum of 0000000260 times. However, this segment group occurs more frequently in the IDoc. Please check the IDoc or the syntax description of the basic type SHPMNT05 (customer enhancement ZSHPMNT05).
Can any one tell me is there any limitation for data records for segment E1EDL37?
Kindly suggest me what is the problem & what needs to be done to fix this.
Thanks in advance.
Regards
Mohammad.

Hi Guys,
This is a problem which occurs throughout lots of SAP systems. This occurs due to someone changing the IDOCSYN table without making the neccessary changes to the EDISYN table.
For more information on this you can check out the note - 370021. Also if you run the following program in your system and make the changes to your IDOC segment, this error will go away.
(Please note that this program is provided by SAP and I just made a small adjustment by adding the COMMIT WORK AND WAIT statement) .
Hope this helps.
REPORT ze1edp19.
TABLES: idocsyn, edisyn, cimsyn.
DATA: old_idocsyn TYPE idocsyn,
      lt_idocsyn TYPE STANDARD TABLE OF idocsyn,
      ls_idocsyn TYPE idocsyn,
      old_edisyn TYPE edisyn,
      lt_edisyn   TYPE STANDARD TABLE OF edisyn,
      ls_edisyn   TYPE edisyn.
PARAMETER idoc_typ TYPE idocsyn-idoctyp DEFAULT 'ORDERS05'.
PARAMETER idoc_seg TYPE idocsyn-segtyp DEFAULT 'E1EDP19'.
PARAMETER occmax   TYPE idocsyn-occmax DEFAULT '99'.
PARAMETER upd_flag AS   CHECKBOX        DEFAULT space.
START-OF-SELECTION.
table IDOCSYN
SELECT * FROM idocsyn
         INTO TABLE lt_idocsyn
         WHERE idoctyp = idoc_typ.
READ TABLE lt_idocsyn INTO ls_idocsyn
                        WITH KEY idoctyp = idoc_typ
                                 segtyp = idoc_seg.
IF sy-subrc = 0.
    MOVE ls_idocsyn TO old_idocsyn.
    ls_idocsyn-occmax = occmax.
    IF upd_flag EQ 'X'.
      UPDATE idocsyn FROM ls_idocsyn.
     COMMIT WORK AND WAIT.
      WRITE: 'Table IDOCSYN updated',
             /,'         Idoctype:      ',idoc_typ,
             /'         segment number: ',ls_idocsyn-nr.
      WRITE: /,'OCCMAX changed from',old_idocsyn-occmax,
             ' to ',ls_idocsyn-occmax.
    ELSE.
      WRITE: 'No UPDATE done in table IDOCSYN',
             /,'         Idoctype:      ',idoc_typ,
             /'         segment number: ',ls_idocsyn-nr.
      WRITE: /,'OCCMAX changed from',old_idocsyn-occmax,
             ' to ',ls_idocsyn-occmax.
    ENDIF.
ELSE.
    WRITE: 'no such record in table IDOCSYN'.
ENDIF.
ULINE.
table EDISYN
SELECT * FROM edisyn
         INTO TABLE lt_edisyn
         WHERE idoctyp = idoc_typ AND
               cimtyp = space.
READ TABLE lt_edisyn INTO ls_edisyn
                       WITH KEY idoctyp = idoc_typ
                                cimtyp = space
                                segtyp = idoc_seg.
IF sy-subrc = 0.
    MOVE ls_edisyn TO old_edisyn.
    ls_edisyn-occmax = occmax.
    IF upd_flag EQ 'X'.
      UPDATE edisyn FROM ls_edisyn.
      WRITE: 'Table EDISYN updated',
             /,'         Idoctype:      ',idoc_typ,
             /'         segment number: ', ls_edisyn-posno.
      WRITE: /,'OCCMAX changed from',old_edisyn-occmax,
             ' to ',ls_edisyn-occmax.
    ELSE.
      WRITE: 'No UPDATE done in table EDISYN',
             /,'         Idoctype:      ',idoc_typ,
             /'         segment number: ',ls_idocsyn-nr.
      WRITE: /,'OCCMAX changed from',old_idocsyn-occmax,
             ' to ',ls_idocsyn-occmax.
    ENDIF.
ELSE.
    WRITE: 'no such record in table EDISYN'.
ENDIF.

26 Error during syntax check of IDoc (outbound)

Hi Experts
I am using TPSDLS - Idoc(outbound).
When we view in WE02 : for few of the deliveries it is working fine , but for some it is giving the following error
26 Error during syntax check of IDoc (outbound)
Please any one help me out for the same
Thanks & Regards
Shaveta

Please check the segments for the idocs in error status in WE02. The segments in the idoc should be in the same sequence as defined while creating idoc in WE30.
For eg. taking the case of invoic02 idoc.
Segment E1EDP01 cannot come prior to segment E1EDK01.
As in WE30 it is defined to come after E1EDK01\
Please reward the points if this information is useful.

IDOC extension (segment cannot be identified)

Hi all,
I have IDOC DEBMAS configured, but when I trigger 1 customer from BD12, the IDOC is failing with status 26 error segment cannot be identified.
In WE82, we have the following:
DEBMAS DEBMAS06 470
DEBMAS DEBMAS06 ZDEBMAS06 470
I only need the standard structure without extension but we have one interface using the same IDOC with extension.
In the partner profile(WE20), i set DEBMAS in the message type, DEBMAS06 in the basic type, and blank in the extension.
What could be missing in the configuration?
Thanks,
Nene

Extension segment is being populated in the user-exit. Only insert extension for specific output type. Closing this thread.

Error 8: Syntax Error? Please Help!!!

~What im trying to do~
> Make a simple animated wallpaper gif for my webpage
Ok, i'll just go step-by-step on what i did to get this error, hopefully someone can help.
1) First off, i have Photoshop CS3 Extended for Windows XP
2)All i did was go to File> Scripts > Browse
3)Then i try load a quicktime clip
4)I get an error that reads *Error 8: Syntax Error, Line 1*
This happens whenever i load a quicktime sequence, and it just started recently. Usually id be able to load up one no problem.

~What im trying to do~
> Make a simple animated wallpaper gif for my webpage
Ok, i'll just go step-by-step on what i did to get this error, hopefully someone can help.
1) First off, i have Photoshop CS3 Extended for Windows XP
2)All i did was go to File> Scripts > Browse
3)Then i try load a quicktime clip
4)I get an error that reads *Error 8: Syntax Error, Line 1*
This happens whenever i load a quicktime sequence, and it just started recently. Usually id be able to load up one no problem.

FRF-00025 Unable to call function. Error message: Syntax error in program

hi,
when we try to import the export file,we are getting the following error in the 24th phase
i.e., check DDIC Password.
The Error is
INFO       2007-10-29 15:53:20 [iaxxrfcimp.cpp:1017]
           CAbRfcImpl::callLibraryFunction
Generating interface for remote function.
TRACE      [iaxxrfcimp.cpp:1056]
           CAbRfcImpl::performFunctionCall
Calling function module: INST_RFC_GET_INTERFACE
WARNING[E] 2007-10-29 15:53:21 [iaxxrfcimp.cpp:1089]
           CAbRfcImpl::performFunctionCall
FRF-00025 Unable to call function. Error message: Syntax error in program SAPLSUNI                                . .
TRACE      [iaxxrfcimp.cpp:1090]
           CAbRfcImpl::performFunctionCall
RFC failure or system exception raised
TRACE      [iaxxrfcimp.cpp:1091]
           CAbRfcImpl::performFunctionCall
Syntax error in program SAPLSUNI                                .
TRACE      [iaxxbjsmod.cpp:657]
           CJSlibModule::showOkCancelBox_impl()
<html>Test logon to SAP System I50 failed.<p>Make sure that the system is started, that the user DDIC exists and that the password of user DDIC is correct.</html>
TRACE      [iaxxgenimp.cpp:1093]
           showDialog()
waiting for an answer from gui
What Could be the solution for this.
waiting for ur reply
SS

Hi Friend,
Please check whether or not there is view missing error recorded in dev_w0 trace file.
if there is , you can try to follow this procedure in order to manually
import the missing view definitions.
All steps must be carried out with the <sid>adm user of the target
system and from the install-directory:
1. In the install-directory
<sapinst_instdir>\...COPY\IMPORTT\SYSTEM\ABAP\ORA\UC\DB
create a file SAPVIEW.cmd with the following content:
tsk: "<sapinst_instdir>\...\COPY\IMPORT\SYSTEM\ABAP\ORA\UC\DB\SAPVIEW.TSK"
icf: "
<YOUR_EXPORT_DIRECTORY>\export\DATA\SAPVIEW.STR"
dcf: "<sapinst_instdir>\...\COPY\IMPORT\SYSTEM\ABAP\ORA\UC\DB\DDLORA.TPL"
dat: null
dir: null
ext: null
Please make sure that all paths are written correctly (in one line) and
the refered files are existant and readable. One exception:
The SAPVIEW.TSK file is created with step 2.:
2. Run from the command-line:
R3load -ctf I
<YOUR_EXPORT_DIRECTORY>\export\DATA\SAPVIEW.STR <sapinst_instdir>\...\COPY\IMPORT\SYSTEM\ABAP\ORA\UC\DB\DDLORA.TPL SAPVIEW.TSK ORA -l SAPVIEW.log
If there's a problem reading the 'SAPVIEW.STR' file, copy the
file to the install directory and adapt the path accordingly.
3. Run the view import by:
R3load.exe -i SAPVIEW.cmd -dbcodepage <YOUR_CODE_PAGE> -l SAPVIEW.log
-stop_on_error
4. Check both the SAPVIEW.log and the SAPVIEW.TSK file whether all views
have been created successfully.
If 4. is okay, restart the central instance and check whether you are
able to log on now. If yes, continue 'sapinst' by the option 'retry' or
'continue old installation'.
I Hope It can be helpful.
With Best Regards
Julia

Error when i try to create a panorama pic. in Ps. i got this message : Error 8: Syntax error. Line: 132 - args.putEnumerated( keyMode٬ typeBlendMode, enumDarken );

when i try to create a panorama pic. in Ps. i got this message : Error 8: Syntax error. Line: 132 -> args.putEnumerated( keyMode٬ typeBlendMode, enumDarken );
everything with last updated the OS , Java , and PS version .
any help pls

What software are you using? PS version. OS version etc. Also check you have all the updates for your version of Photoshop installed. That your only selecting image files to be stitched. That a javsscript error message from one of the Stack Script Only that get used when you use Photoshop Photomerge Script.

Idoc Error - EDI: Syntax error in IDoc (segment cannot be identified)

Similar Messages

Maybe you are looking for