Error in IDOC Processing

hi all ,
I am getting error No. 26 while processng IDOC. error is Segment Cannot be identified,
Mandatory segment missing. how can i resolve that error
actually i want to add one zsegmant to standard basic type DESADV01.
please give me a detail stepwise procedure for adding that segment with transaction
is there any type of setting that i have to maintiain after adding that segment.
please give a solution.
thanks,
vinod

go to BD56 tcode ..give the segment and check is it available with DESADV01.If no....go to WE30 create zidoc with your own segment...now extend your DESADV01 idoc type by selecting the radio button extension idoc type and add here your own zidoc...in the first screen you select as this segment as mandatory.
<REMOVED BY MODERATOR>
Dara.
Edited by: Alvaro Tejada Galindo on Apr 22, 2008 3:51 PM

Similar Messages

BOM mapping with change number error during IDoc process

Hi all,
i am creating BOM using IDoc BOMMAT04.i have checked this IDoc will use FM IDOC_INPUT_BOMMAT inside.
in this function module, it is using FM CSAP_MAT_BOM_CREATE and CSAP_MAT_BOM_MAINTAIN to create and change.
currently, creation and deletion is success. but when change, if the change number passed as an input parameter, the IDoc process error saying that the BOM header not allowed to update for read-only field.
if i not pass the change number, the change will be success, but no change number displayed in the item. that is not the user expected.
and if i delete the bom with change number, create a new BOM for the same material is not aloowed, saying that BOM already existing.
it seems that CSAP_MAT_BOM_CREATE and CSAP_MAT_BOM_MAINTAIN cannot support much. it is limited.
can anyone have any good solutions? thanks!

yeah, for the change, i have solved it.
but currently, if i delete the existing BOM with a change number, the re-creation is not allowed by the IDoc saying that the BOM already existing.
if i delete in CS02 without change number, it deleted from DB and can be re-create.
but if delete in IDoc without change number, it failed saying that local BOM can not be deleted by ALE.
do you have any solution? i want to implment in IDoc: delete existing BOM and create a new one for the same material with change number. (currently the standard IDoc FM not support BOM group)

Error During IDoc Processing

Hi friends,
i want to transfer data in between two systems.
i have created my own message type = ZSACH
Basic type = ZSACH1
segement = ZSACH
model view = new_model
when i am execuiting this IDOC by using the program i am getting the error as
EDI: Syntax error in IDoc (segment cannot be identified)
here i am giving the coding what i have write in my program
parameters :p_logsys like tbdlst-logsys.
data : gen_segment like edidd-segnam value 'ZSACH1'.
data : control_dat like edidc,
       control_dat1 like edidd,
      gen_data like zsach .
tables : zsach1.
data: begin of inttab occurs 0,
        lname type zsach1-lname,
        fname type zsach1-fname,
      end of inttab.
data :
      int_edidd like edidd occurs 0 with header line,
      int_edidc like edidc occurs 0 with header line.
select * from zsach1 into corresponding fields of table inttab.
if sy-subrc ne 0.
message 'no data' type 'I'.
exit.
endif.
control_dat-mestyp = 'ZSACH'.
control_dat-idoctp = 'ZSACH1'.
control_dat1-segnam = 'ZSACH'.
control_dat-rcvprt = 'LS'.
control_dat-rcvprn = p_logsys.
loop at inttab.
gen_data-lname = inttab-lname.
gen_data-fname = inttab-fname.
int_edidd-segnam = gen_segment.
int_edidd-sdata = gen_data.
append int_edidd.
endloop.
call function 'MASTER_IDOC_DISTRIBUTE'
exporting
    master_idoc_control                  = control_dat
*   OBJ_TYPE                             = ''
*   CHNUM                                = ''
tables
    communication_idoc_control           = int_edidc
    master_idoc_data                     = int_edidd
exceptions
   error_in_idoc_control                = 1
   error_writing_idoc_status            = 2
   error_in_idoc_data                   = 3
   sending_logical_system_unknown       = 4
   others                               = 5
if sy-subrc <> 0.
message id sy-msgid type sy-msgty number sy-msgno.
else.
loop at int_edidc.
    write :/ 'IDOC GENERATED',int_edidc-docnum.
endloop.
commit work.
endif.
<Added code tags>
can anyone give better solution for this error..
i have searched in SDN but i can't get the better document
thanks in advance.
Regards,
kk
Moderator Message: Please use "code tags" to format your code.
Edited by: Suhas Saha on Nov 9, 2011 12:59 PM

Hello kk,
It is very clear from the error message
EDI: Syntax error in IDoc (segment cannot be identified)
that there is some problem with the segment name.
When i look at your code snippet i can see there is a mismatch in the segment names passed in the IDoc control rec & the data rec.
control_dat1-segnam = 'ZSACH'.
int_edidd-segnam = gen_segment. "gen_segment like edidd-segnam value 'ZSACH1'
BR,
Suhas
PS: Before searching in SDN try to put-in some self-effort, saves time actually

Error in IDOC processing - Message no. VU 014

Hi All,
I got error while processing IDOC manually as:
" Incompletion: Vendor : Account number of vendor or creditor (VBPA -LIFNR ), error group: 08"
Details of Error message are as below:
Message no. VU 014
Diagnosis: The incompletion check reveals, for analysis purposes, any incomplete documents.
The message contains:
1. A description of the incomplete document
2. A technical entry, telling you which table field has been checked
3. A the error groups in the transaction from Customizing for Incompletion Log.
Procedure
One solution is to deliver the affected document in the screen (Create delivery with reference to order), and to edit and save the delivery following the menu path: Edit -> Incompletion.
In certain circumstances, you can change Customizing so that
the checked field is no longer assigned to the error group
or
assign another error group to the document type /item category
or
permit the delivery as a subsequent function.
I am confused about what could be the root cause of the error and how to solve it.
The Important thing is, when IDoc is run in Automatically(batch run), then it is successful with no any error but it gives this error when i run it manually.
Pl. guide me to solve this problem.
Thanks,
Jai.

Hi Bernd,
Thank you for your mail.
The Note 991410 is related to the IDoc status 53. I stucked with the IDoc status 51.
IDoc error message is in status 51. But still I am looking all other alternative inculding one you suggested.
Thanks you very much.
Jai.

Error in idoc process

I am new to EDI / IDOC. Manual bill is not being created.
In TCODE EA18 I am facing an error that the EDI 810 failed to process , idoc - Application document not posted - Datex Process Error.
Can anyone suggest me what to do for resolving this error.
Thanks in Advance.

Hi,
change names while creatingwork are for that.
maintain order of the segments in order as for idoc.
check whether you are maintaining orderly or not.

Syntax error in IDOC process

Hi,
We are getting syntax error in ORDERS01 IDOC. I have checked the E1EDP19 segment's maximum occurence is 5 which is a child segment of E1EDP01.
But the my outbound IDOC had more than 5 occurences in the segment E1EDP19.
It look to me that because of this we are getting syntax error. Please correct me If I'm wrong.
How can I change the maximum occurence value in an standared segment.
Thanks,
Dharmendra

Hi,
change names while creatingwork are for that.
maintain order of the segments in order as for idoc.
check whether you are maintaining orderly or not.

Error in IDOC generation

Hi Gurus,
I have got an Error in IDOC Processing from other interface.
The IDOC status is 51 and we are using it to create Promotion Deal in
SAP ERP through IDOC from other interface.
The Error i am getting in Status Record is that "Promotion is Duplicated
along with Promotion Deal Number"
I have also checked the Promotion Deal No in VB 33 but it is not existing.
Please could you suggest where is the possible error.
I have also checked the Control Record it is correct.
Awaiting for response.
Thanks,
Sam.
+

Hi,
Reprocess the IDOC by using the T.Code "BD87".
Even if the same error persists,try to change the data manually by using the T.Code "WE19".
Check with the ABAPer for debugging the code.
Regards,
Krishna.

Inbound Idoc processing issues - Partner Profiles - error status 56

Hello All,
I'm having a little difficulty posting an idoc coming from MDM. It's a CREMDM04 xml coming from an MDM system. It is getting mapped through PI and is being split into ADRMAS02 and CREMAS04 Idocs. The message is being passed through XI and being posted to the ECC system, but certain fields in the EDI_DC40 header table are not being populated correctly (i believe). I'm using nothing but standard mapping/material from the SAP Business Content for XI. After looking through the standard XSLTs i cannot find the field-to-field mapping where the fields below are being populated.
The RCVPOR value (SAP[SID]) is correct when i view it in SOAP Header, but does not appear in the remote system under the receiver port for the inbound idoc.
The RCVPRN value ([String Value]) is incorrect in the SOAP Header and does appear in the remote system under the receiver partner number for the inbound idoc. How is the RCVPRN value being populated?
SOAP Header in IDocOutbound tag
<SAP:RCVPOR>SAP[SID]</SAP:RCVPOR>
<SAP:RCVPRN>[String Value]</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
I've been trying to trace down the string value for the RCVPRN, but i cannot find it anywhere. Perhaps i'm just overlooking it?
When i set the proper values (port = SAP<SIDofECC> and partner number = <LSnameof ECC>) using WE19 in the remote system then the partner profile is found and i'm left with different error to please specify an address group.
Any help is very much appreciated! :-D

Hi Jason ,
Just check out if you have done the following steps most of us make minor mistake here ....... I think this would solve your problem
To Configure the IDOC SCENARIOS ,PROCEED AS FOLLOWS
STEP 1:ALE SETTINGS TO POST IDOC INTO SAP R/3
We need to do the following settings in XI
1) Create an RFC Destination to the Receiving System in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a) Select Create New button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client
d) Enter the RFC Destination created in XI towards R/3
e) Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) Create an RFC Destination to XI in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Inbound Parameters (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Inbound Parameters.So click on ADD TO Create Inbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Message Type and Process Code.
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
do let me know if it helped
Edited by: Tom Jose on Feb 21, 2008 9:04 AM

Error In inbound Processing IDoc

Dear All,
I am facing error while inbound processing of IDoc
In status record of IDoc following errors are occuring
Status 60 : EDI: Syntax error in IDoc (mandatory segment missing)
The segment E1MAKTM has the attribute 'Mandatory' in the syntax description of the basic type MATMAS05 (customer enhancement ). However, the segment is missing in the IDoc
Status 51: Application Document not posted
Log details :
Error : Material Number should be filled.
When i checked IDoc all 4 fields in E1MAKTM have the values in inbound IDoc.
Please guide me how to resolve these issues so that IDoc will be posted and Material Master will get created in reciever system.
Thanks

Hi Praveen,
I checked the data in IDoc for this segment.
It is ok as required in basic message type.
e.g. the error says that mandetory segment E1MAKTM is missing.
when i check basic type
MSGFN : Function
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
SPRAS : Language Key
internal data type : LANG
Internal length : 000001 characters
Position in segment : 002, Offset : 0066. external length : 000001
MAKTX : Material Description (Short Text)
internal data type : CHAR
Internal length : 000040 characters
Position in segment : 003, Offset : 0067. external length : 000040
SPRAS_ISO : Language according to ISO 639
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 004, Offset : 0107. external length : 000002
is information.
and data in segment of IDoc is
MSGFN     005
SPRAS     E
MAKTX     MANATA2000 TEST ALE
SPRAS_ISO     EN
which i think is ok.
I have no clue why this syntax error is coming.
Thanks
Niketan

Error message when processing IDoc

Hi there,
Greetings from Buenos Aires, Argentina.
I'm trying to use the Migration Workbench in order to transfer to SAP the material master data.
I have created an LSMW Objet and selected, under Mantain Object Attributes >> Object Type and Import Method, the IDoc option. The message type will be MATMAS and the Basic Type will be MATMAS05.
I have maitained the IDoc Inbound processing, created the LSMW Port and the Partner Profile. In the latter, under Inbound Parameteres, I have created and inbound parameter with the MATMAS Message Type and MATM Process Code.
I have created structure relationships for the following target structures: EDI_DC40, E1MARAM, E1MAKTM, E1MARCM and E1BEWM.
After being one or two couple of hours going and coming over the application log after running over and over again the step 14. IDoc Processing, and having filled with '/' the obligatory fields, I still am not able to generate it successfully.
The problem I'm having is, it keeps asking the DISMM (I think the name is MRP Type) field, and since I have not created a conversion rule or source field for it, I recieve the error message 72 from the M3 message class
I understand that though the MM01 transaction, if the MRP View isn't activated, this field stops being mandatory. So I need to know, if any, the way to make the IDoc processing not to ask this field, since the MM consultant has said it's not necessary to introduce it.
Thanks in advance.

in the step 5 Maintain Field Mapping and Conversion Rules
in the strcture E1BPMATHEAD   put the below condtion
E1BPMATHEAD                    Header Segment with Control Information
for the MRP veiw WERKS and DISMM is mandatory fileds if you are not getting the any one of the value from the file ,skip the MRP view using below condtion.
MRP_VIEW                     Material Requirements Planning (MRP) View
                    Code:    * Target Field: E1BPMATHEAD-MRP_VIEW Material Requirements Plann
                             IF NOT matmas-werks IS INITIAL AND "
                                NOT matmas-dismm IS INITIAL.
                               e1bpmathead-mrp_view ='X'.
                             ENDIF.

Error in outbound processing:ALE/IDOC

Dear all,
I am getting an error in outbound processing as follows(I have extended the BD12 IDOC for customer master).
The issue is that there is no hierarchie of segments in IDOC transaction we05.(Thogh the hierarchie can be observed in WE30)
EDI: Syntax error in IDoc (segment cannot be identified)
Message no. E0078
Diagnosis
The segment Z1KNA1M_ADRC does not occur at the current level of the basic type DEBMAS06 (extension ).
This error can have several reasons:
u2022     The segment Z1KNA1M_ADRC is assigned to a group whose header segment does not occur.
u2022     The segment Z1KNA1M_ADRC does not exist in the syntax description of the basic type DEBMAS06 (extension ).
u2022     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 DEBMAS06 (extension ).
I will be thankful if anybody can help resolve the issue.
thanks.
Edited by: sanjivrd on Aug 4, 2009 2:17 PM

hi,
after adding those segments you need to release it.
check it menu you can see the release option, you need to release it.
then only it will work
[Refer following link|EDI: Syntax error in IDoc (segment cannot be identified)]
In the menu edit-> set release
click on it and release
Even check If the Hierrarchy of the segment is correct. This also will result in Syntax Errors.
thanks & Regards,
ShreeMohan

Error in re-processing inbound idocs of status 51

Hi
We are facing problems in reprocessing inbound idoc from BD87 transaction
We have an inbound process code 'STA1' which is pointing to a standard task 'TS30000206'. we have an errored inbound idoc(status 51) of message type 'STATUS' ( standard status change idoc pointing to process code STA1 for a valid port. Whenever we try to process it using BD87 transaction, we are getting errors B1033-'No function module for input process code STA1'.
We dont understand what we were missing. When we try the same for a process code which points to a function module, BD87 reprocesses it correctly.
We tried adding an entry in BD67 with an inbound function module 'APPL_IDOC_INPUT1'. Note that we still had the process code pointing to the same task. This time BD87 reprocessed idoc, but gave 51 again saying that 'Function module not allowed: APPL_IDOC_INPUT1'.
Any pointers or help in this regard will be highly appreciated.

Hi,
Please check IDOC TYPE, MESSAGE TYPE & PROCESS CODE and also check the we30, we42. & try BD87 reprocess of an IDOC.

Error on outbound processing (- to IDoc), nodetailed error message

Hi guys!
I'm facing a problem with sending IDocs to R/3. My messages have red flag in outbound status, but there is no detailed error message. Everything seems to be ok, but my IDoc doesn't arrive to R/3 and there is that red flag in XI.
What could cause this? It seems like there is some communication problem. Any ideas?
Thank you,
Olian

Hi,
IT will give the status number,what is the status number in IDOC check it and update the thread.
if u find its a data problem u can debugg the FM,go to WE19 and give ur IDOC number and there u will find the option start out bound processing form this opion u can debugg the code and know wat is the error.
Check ur ALE settings.
STEP 1:ALE SETTINGS TO POST IDOC OUT OF SAP R/3
We need to do the following settings in XI
1) Create an RFC Destination to the Sending System in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client
d) Enter the RFC Destination created in SAP R/3 towards other system
e) Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) Create an RFC Destination to XI in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client user & Password details of Destination system
h) Test the connection and remote logon.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Outbound Parameters (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Outbound Parameters.So click on ADD TO Create Outbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Receiving port, Pack size=1 and Basic type
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
5) Create Customer Distribution model in the transaction code BD64
1) Click on the Create modal View button and enter the short text, Technical name etc as shown below
2) Now select the created model view and click on Add message type button .A pop up box appears, enter Sending system, receiving system and message type
3) Save the Distribution model
Generate Partner Profiles
Click on Menu Item Generate Partner Profiles
It leads to the next transaction where in the selection screen you have to provide Model view name, Partner System logical system and execute
Then, you will be intimated about the partners, port creation, and outbound parameters creation
4) Distribute Customer Distribution Model
In the menu item GO to Edit->Modal View-> Distribute to the destination client
Popup window appears ,press Enter
You will be intimated about the the Modal View Distributed
Regards,
Phani
Reward points if Helpful

Error message during processing in BI

1.i am loading the data into infoobject.
2.got error in text data load.
3.master info object have compound obj 0COUNTRY
4.and other normal fields are 0TXTSH,0LANGU,sold-to-party.
5.there is no PSA in this..its direct update to INFOobject.
The error message is:
Error message during processing in BI
Diagnosis
An error occurred in BI while processing the data. The error is documented in an error message.
System Response
A caller 01, 02 or equal to or greater than 20 contains an error meesage.
Further analysis:
The error message(s) was (were) sent by:
Update
Diagnosis
There are duplicates of the data record 2. with the key '3.' for characteristic 1..
Procedure
If this message appears during a data load, maintain the attribute in the PSA maintenance screens. If this message appears in the master data maintenance screens, leave the transaction and call it again. This allows you to maintain your master data.

Hi KP,
In the details tab,
1.under Transfer (IDOC and Trfc):
   Data Package 1 : arrived in BW ; Processing : Error records written to application log
2.Processing (data packet): Errors occurred
   Update ( 0 new / 0 changed ) : Errors occurred
   Error records written to application log
   0TRZONE : Data record 1 ('0000000001D ') : Duplicate data record
   0TRZONE : Data record 2 ('0000000002D ') : Duplicate data record
   Error 4 in the update
3. Process chain error
these are the error details.

Send mail to a specific user group when an Inbound Idoc processing fails

I am using standard Message type DEBMAS, but the process code is customed (say ZDEBM as the function module is customed). Can you tell me what configurations are required to activate the error notification message to a user when the inbound idoc fails?

hi,
i think u need to check tcode swu3 for automatic workflow customizing and check in we40 (error AND STATUS PROCESSING) whether the processing code is assigned to the workflow task.
if it is assigned,the workflow will be automatically triggered and the mail will be sent to the user by itself.
ALE error handling uses workflow. A standard task is provided for each message type. Task TS20000051 is used for all BAPIs.
Workflow functions as follows:
A task (work item) is generated for the error handling and stored as a message in the inboxes of the employees responsible.
If one of these employees processes the work item, the standard task method for error handling is started. The user can, for example, restart IDoc processing.
If the IDoc is processed successfully, the work item is deleted from the inboxes of all the employees involved.
For this procedure to function, the employees responsible for a particular message type and partner (sender or receiver) must be defined as follows:
1. A hierarchy of organizational units (for example, "sales office") and positions (for example, "customer officer for customer X") is created and employees are assigned to it.
2. The standard tasks for error handling (for example, an error related to an inbound sales order) are assigned to the relevant organizational units or positions (for example, "sales office").
3. The organizational unit, position or employee responsible for dealing with the error are specified for each partner and message type in the partner profiles.
If an error occurs, the system determines:
1. The employees responsible using the staffing schedule of the organizational unit or position linked to the standard task.
2. The employees defined in the partner profiles (using position, user ID, or organizational unit).
3. The employees appearing in both groups represent those who will receive a work item in their inboxes.
regards,
pankaj singh

Error in IDOC Processing

Similar Messages

Maybe you are looking for