Adding EDI (856) errors to workflow

We use workflow but don't see EDI-856 errors there (message type DESADV, basic type DELVRY03).
Does anyone currently have EDI errors in workflow and can assist in how to add them to workflow?
Regards,
Michelle

WE46- all active.
Maybe there is a place to define a new error? The business wants EDI 856 status '51' idocs added to workflow. Any other ideas?

Similar Messages

IDOC DELVRY05 TO EDI 856 - Mapping problem

Hi all,
i'm currently working on a outbound mapping with the delivery idoc (DELVRY05) and the EDI 856 (Advance Shipping Notice Definition)
The problem is that i can't map the items for every pack in the structure because the ocurrency doesn't match.
The EDI 856 has a segment called G_SHL (ocurrence 0.200000), that i replicated 4 times for shipping, order, pack and item data
And this segment has a subsegment called G_SHL/S_HL (ocurrence 0.1)
RESULT DESIRED GIVEN BY THE CLIENT: (1 pack/1item)
3     HL1*S~                        ======> S: shipping, 1 hierarchy)
4     TD1CTN251***G223.997*LB~
5     TD5*2ABFSM*CC~
6     REFBM003030987~
7     REFCN086044619~
8     DTM01120080128*180610~
9     DTM06720080204~
10     FOB*PP~
11     N1SFStiefel Labs~
12     N4DULUTHGA*30096~
13     HL21*O~ ======> O: order, 2 hierarchy, 1 was the previous hierarchy)
14     PRF*4064561~
15     HL32*P~ ======> P : Pack, 3 hierarchy, 2 was the previous hierarchy
16     MANGM00000734620052976193~
17     HL43*I~ ======> I: Item , 4 hierchay, 3 was the previous hierarchy
31     LIN*UP073462150651LT45X5147ND00145150605~
32     SN1*12EA~
33     DTM03620090930~
34     HL52*P~ ======> P : Pack, 5 hierarchy, 2 was the previous hierarchy
35     MANGM00000734620052975189~
36     HL65*I~ ======> I: Item , 6 hierchay, 5 was the previous hierarchy
37     LIN*UP073462150651LT45X5147ND00145150605~
38     SN1*12EA~
39     DTM03620090930~
40     HL72*P~ ======> P : Pack,7 hierarchy, 2 was the previous hierarchy
41     MANGM00000734620052975196~
42     HL87*I~ ======> I: Item , 8 hierarchay, 7 was the previous hierarchy
43     LIN*UP073462150651LT45X5147ND00145150605~
44     SN1*12EA~
45     DTM03620090930~
46     CTT*8~
47     SE479220014~
As u see, all packs belong to "2 hierarchy" (order), and items to their correposding pack
(has a comment, the "hierarchy number" is always given by a counter so u won't find the exact number again)
so, the client wants us to create an structure that is like this..
1º Pack
1º item
2º item
2º Pack
1º item
2º item
(the example has only one item, but they say that is going to be with many items)
- The problem is that the structure data of the Idoc doesnt match EDI 856 structure
E1EDL37 (0.99999) -
Pack data -
G_SHL (0.200000)
E1EDL37/E1EDL44 (0.99999) -
Item data -
G_SHL/HL (0.1) <====
i was doing different G_SHL for pack and items but that leaves me with a wrong structure, and with all the hierarchy data wrong for items (since the mapping can't see which item belong to his pack)
1º Pack
2º Pack
3º Pack
1º Item
2º Item
3º Item
- How can i map the structure Pack/item if in the idoc got too many item positions for only one EDI corresponding segment??
Thanks in advance!

Alains,
We have the same tear, pack and item problem with one of our customer in one of my project. To acheive this result with the standard schema is not possible because this is a custom one.
So I would suggest to change the schema in BIC like the occurrence and within the third G_SHL you should have S_HL and within this you should have a S_HL so that for every pack you will have multipe items.
The bottom line is to have the schema as required by your mapping. Once you change the schema deploy the maps in J2EE and use them else it will throw an error in RWB.
Regards,
---Satish

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

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.

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

Outbound 856 - Error generating an IDOC

Hi Everyone,
We have a scenario where we need to generate an IDOC for Advance shipping notification for 856 outbound, the basic settings required to do the same are done using the message type DESADV and IDOC type DESADV01. However the IDOC is not getting generated and encountering an error while generating an idoc for 856 outbound from VL02N transaction, when checked the processing log the error with the message 'IDoc type DESADV01 cannot be processed by IDOC_OUTPUT_DELVRY' is displayed. Following Partner profile details are maintained in WE20 for the basic idoc type DESADV01,
processing code DELV ,
message type 'LAVA'
application V2,
also checked the fm attached in WE41 for the process code and found that it is the same. Can anyone give me a clue as to why IDOC is not getting generated for this message type,
Your quick response would be highly appreciated,
Rgds,

Hai sailatha,
Just check these links you may get some idea.........
edi 856 inbound
Shipping Notification
Advance Ship Notice
Regards,
Srikanth.

Error in workflow while linking goods receipt document with parked invoice

Hi All,
I parked document using Tcode MIRO, when WF has been executed and goods receipt document has been created.At the time that we tried to link this goods receipt to parked invoice document in the workflow,The problem happens with work item saying the status as Error. See the below error.
MIRO Invoice: 801061193 2010 Item: 000001 13.09.2010 09:24:58 Error AP Workflow for MIRO/MIRA Parked Invoice
Can anyone advice why it is coming so?
Thanks in advance.

Hi
In SWEL go to workflow trace and see what exactly is the error. This error description is too generic to arrive at soln.

Error in Workflow for PR Overall Release

Dear SAP Fans,
I am getting error in workflow (WS20000077) after release of Purchase Requisition with first person and getting message in OutBox with the following errors and is unable to go to next person's Inbox for release PR.
   Error when creating a work item
   Error when processing node '0000000004' (ParForEach index 000000)
   Error when creating a component of type 'Etapa'
   Error when starting work item 000000392108
   Agent determination for step '0000000004' failed
   Error in resolution of rule 'AC20000026' for step '0000000004'
   No configuration for workflow WS20000077 version 0001
   Work item 000000392108: Object FLOWITEM method EXECUTE cannot be executed
How can I correct the above errors. Please help me !!!.
Thanks in advance,

HI,
Just a thought,
Please check, If some one changed WF-USER password.
also check if the WF-USER is a Service user and not dialog user.
Regards,
-Venkat.

Read EDI-856 interface data in ABAP program

HI Experts,
I have a requirement to read the incomming EDI-856 interface data from ABAP program and generate an IDOC. I have gone through few EDI-856 documents and theformat in which to read the data .
Request you to let me know the code logic , function module to use or if you have any document which can help me in the development.
Thanks in advance
Regards
Santosh

Please help regarding
First could you please help me regarding the SCN search option?
please always try to attempt from your side if not able to solve than search in SDN finally you may land on SDN with thread.

Error on Workflow email notification in oracle 11.5.10.2

Anyone seen similiar error on Workflow email notification in oracle 11.5.10.2
UNEXPECTED:[fnd.wf.bes.server.SystemLoader.getLocalSystem]:Caching disabled due to JTF exception: oracle.apps.jtf.base.resources.FrameworkException: CacheComponent not registered (KEY=FND_BES_SYSTEM_CACHE) (APP=FND)
UNEXPECTED:[fnd.wf.bes.server.AgentLoader.getAgent]:Caching disabled due to JTF exception: oracle.apps.jtf.base.resources.FrameworkException: CacheComponent not registered (KEY=FND_BES_AGENT_CACHE) (APP=FND)

I do not see any similar issues reported in MOS website that could be relevant to Workflow.
Can you find any errors in the database log file?
Please run the diagnostics scripts in these docs and see if it helps.
Troubleshooting Oracle Workflow in Applications 11i [ID 262011.1]
11i: Oracle Workflow Cartridge (WF): Workflow Java Mailer Diagnostic Test [VIDEO] [ID 1148948.1]
11i: Oracle Workflow Cartridge (WF): Workflow Health Check Diagnostic Test [VIDEO] [ID 1148953.1]
11i : Oracle Workflow Cartridge Workflow Java Mailer Setup Test [ID 274764.1]
If the diagnostics scripts did not help then I would suggest you log a SR.
Thanks,
Hussein

Missing flatfile of EDI 856

Hi,
Thanks in advance.
EDI 856 program was extracted from Oracle by passing the customer name as parameter, however one of the delivery number for that partcular customer was never made available for EDI to pick up to generate a flatfile.
Can anyone please tell me the cause of missing the 856 data.
Thanks
Satya.
Edited by: user11048416 on Aug 5, 2009 4:35 AM

Hi,
Check with your team there can be some docs on the seeburger modules...
which can be used for the same..
basically you need to take care of generation of the no of segments as per your requirements ...but for the segment count..blah..
some stuff will take care by seeburger..
I dont have any documents regarding this....search SDN you can find some..
HTH
gud luck
Rajesh

Error handling workflow not getting triggered

Hi all,
I'm creating a outbound IDoc. And for error handling workflow.. I created a organization structure in PPOME and assigned users. I gave this position number thus created in the partner profile in post processing permitted agent tab.
But when the Idoc is in error, this is not coming to my inbox.
Can someone please help me with this.. and let me know what went wrong.
Thanks in advance.

Here you need to be careful,
if the agent assignment is not maintained properly, there may be a chance everyone in the organization will get the item.
I hope you have created a single workitem for error handling. goto additional data-> agent assignment-> maintain. make sure the attribute is defined as general forwarding allowed. or you maintain the role/position/user/whatever.as the possible agents. still you dont get the result, debugging the default rule in the task ->default rule -> agent.
hope this helps.
with regards,
Sudhahar R

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

Adding EDI (856) errors to workflow

Similar Messages

Maybe you are looking for