Idoc failure(outbound process)

I had worked with the transactional data (INVOICE) and message control technique which has triggered with an idoc but it fails to deliver to the reciever system. so, can trigger the idoc for sending the invoice next to this one with out solving the previous issue.
Thanks,
Mammula Raju.

Firstly, I didn't understand your question completely. If I understand what it is, then you're having an issue sending IDOC outbound and the receiver receiving it?
If this is true, you might want to look at the port setting. Check the folder which is configured to the port and if your EDI/ALE subsystem is looking at the same folder to pick up the data.
Additionally, what is the error you're receiving? Is the error being sent back by the subsystem that receiver is not getting it? If that is true then there is something wrong in your sub system layer. If this is in test, then note that you might receive this error because you do not want to send the data to your trading partner.
However if this is in production, you have looked in the areas I've mentioned above and still have an issue, then please elaborate a bit more on the error.

Similar Messages

REG: Error in IDoc adapter outbound processing

Hi All,
      I had a couple of doubts regarding these IDoc's.
1)        I am dealing with the web services to IDoc Scenario. When i am activated my wed services it               is giving an error like
"IDOC_ADAPTER.ATTRIBUTE_BE_NOT_SUPP" and "Only asynchronous processing supported for IDoc adapter outbound processing"
Can any one help me to Solve my Problem
2) How to find out whether the IDoc is of synchronous or Asynchronous mode
    and how to handle the synchronous type of IDoc's
Thanks in advance.
with Regards,
Kalyan Dannapaneni.

Hi Kalyan,
IDOCs are only Aynchronous (EO or EOIO).
If you want to call Synchronious, you will have to find remote enabled function modules (RFCs, BAPIs).
Or you have to use the ccBPM Synch-Async pattern to have an synchronos call passed to an IDoc, waiting for the Acknowledgement. In your situation I would check if a similar BAPI/RFC exists on your Backend SAP system.
Best regards,
Silvia

MIRO - Idoc for outbound process ( LIV)

Friends,
SAP has to send the following data to Oracle Financials. XI is the interface. So I need to identify the idocs used in LIV ( Invoice Verification) module.
Can any one help me what idoc / bapi should i use for the below outbound process.
Vendor invoice and credit memo
Also, i heard transactional data cannot be triggered by programs RBDMIDOC and it will be send automatically.
How can I send the idoc automatically in the outbound ALE layer. Is theres any message type to set up or any program to be execute. In other words , how the change pointer is triggered for the transactional LIV data.
Regards
Raj

Raj,
It really depends on where you are sending yor IDOC or whom you want to be informed.. If you think it is just for records.. After reding your initial description.. if it is an ERS based invoice, you could use ERS, else
Create a new condition table and include all teh fields that you want.. make sure you do not mix the item fields with the header,
Include that table in a custom access sequence that you create and assign a new message type-- custom again..
That is the only way you'd actually be able to capture all teh fields and information you want.

Inbound & outbound process

Hi All,
I am new to ALE. I want to know what is the actual process behid inboud and outbound services in ALE.

Hi,
1.Here out bound means sender.Inbound mens --receiver.
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
There are two filtering in IDoc.
Segment Filtering:
Segment filtering can be achieved using T/Code BD56. Here you can suppress a whole segment irrespective of data inside it . You have to give Message Type / Sender Prrtner / Receiver Partner.
Data Filtering:
Data filtering can be done in dustribution model (BD64) where you can restrict whole IDOCS or partials IDOCS to be send based on data in fields inside IDOC depending on whether the segment in which you filter is at the highest level or at a lower level. For example in MATMAS if you put a filter of E1MARCM for a particular plant , only data for this plant will go and other plants will be ignored.
Please check this link for more information.
http://help.sap.com//saphelp_470/helpdata/EN/0b/2a611c507d11d18ee90000e8366fc2/frameset.htm
Regards,
Shiva.

ALE - Idoc not getting processed automatically, instead going fine in Debug

Hello All,
I have a problem with Inbound idoc processing.
IDoc settings were made 'immediate processing' in WE20, and the process code is set correctly and the attached of Z-Fun. module to process the idocs to process code.
The error in inbound side is as 'Function module not allowed: APPL_IDOC_INPUTI' 51 status. Am sure i have to do some thing with ALE settings.
Can some body help me with correction step or sequence of steps for this ALE process.
Thanks & Regards, Jilan

Hi Jilan,
Plz follow the steps:
ALE Configuration:
     WE30 - IDOC type creation
     WE31 - Create segment
     WE81 - Message type creation
     WE82 - Link IDOC type to Message type
     SE37   - Create Inbound Function Module
     BD51 - Maintain entry for Function Module
     WE57 - Maintain
     BD57 - Link Function Module, IDOC type and Message type
     WE42 Create Inbound Process Code
     BD67 - Link Process code to Function Module
     WE20 - Create Partner Profile
     BD64 - Display Distribution Model
     WE02 - IDoc List, Display all Inbound/Outbound IDocs
     WE14 - Outbound Processing of IDocs
     BD20 - Inbound Processing of IDocs
1st Step:   Create a Segment ( WE31)
         Segment is a structure for passing data in IDoc. It actually contains the IDoc data, just like the DDIC table/structure. Segment is created with all the required fields. Then Save it. But, to actually use this Segment, you have to Release the Segment, otherwise u cant use the Segment, by menu, EDIT--> Set Release.
         Now, if you want to do some change to this Segment, u cant, unless & until u Cancel the Release, by Edit--> Cancel Release.
2nd Step:   Create IDOC Type ( WE30 )
        After creating the Segment, now we have to create the IDoc Type. IDOC Type is like an envelop of a letter, which contains the data inside it, & also some more information like address. IDoc type can be Basic Or Extended.
       Basic IDoc Type: Using some SAP existing IDOC type (ex. MATMAS) or Custom IDOC type.
       Extension IDOC Type: When we need some fields extra to an existing IDOC type, then we can extend that Basic Idoc Type by another Segment. This is called Extended idoc type
3rd Step:   Create Message Type (WE81)
     Message Type is like the Postman for sending the Letter.
4th Step:   Attach Message Type to the IDOC Type (WE82)
5th Step:   Create a Function Module (SE37)
       Write the Processing logic in a Function Module.
6th Step:   Mention the IDOC Type, i.e, 0/1/2 (BD51)
7th Step:   Assign the Message Type, IDOC Type & Function Module (WE57)
8th Step:   Create a Custom Process Code (WE42)
9th Step:   Attach the Function Module to the Process Code (BD67)
10th Step: Execute Inbound IDOC s (WE19)
Example Function Module: IDOC_INPUT_ORDERS (Standard FM to create Sales Order).
reward is useful,
regards,
Tanmay

IDoc Outbound processing

Hi All,
I am doing IDoc to File scenario. I have my IDocs in AXI system and XI in ZXI system.I want to send idocs from AXI to ZXI. I have configured the following in AXI :
RFC dest to ZXI (Dest4ZXI)
Transaction Port to ZXI having RFC dest as Dest4ZXI
Logical system for receiver file system
Partner profile for receiver file system with outbound parameter
and the following configuration in ZXI:
RFC dest to AXI (AXICLNT100)
Port to get IDoc's metadata from AXI (SAPAXI) having RFC dest as AXICLNT100
In SLD, i created a tech sys and business sys for sender system AXI and then i created a scenario in ZXI for IDoc to File. In IR, imported the idoc and created all other objects till interface mapping. In ID, assigned the business system, created a service for file receiver and created rec det,int det and rec agreement.
Using Idoc test tool i started the outbound processing after giving the data and control record and got the IDoc sent successfully message.
Control record values:
Receiver: port = (port created in AXI), partner no = (LS File receiver sys created in AXI)
sender : port = (SAPAXI - port creted in zXI), partner no = (AXICLNT100 - LS created in sld - which is same name as RFC detination created in ZXI)
If i check in we05, its green flag. But in sm58, error status message for the idoc is showing as "No service for the system SAPAXI for client 100 in Integration Directory.
Note: I am using a custom IDoc with 8 fields.
Kindly reply if my descriptions are not clear!
Appreciating all help.
Thanks in advance,
Uma

Hi Uma,
<b>Have u imported the Business System as Service or not?create u r cc in the service for that bs only</b>
If not just try with it..
If the sender system is maintained as the business service then we have to edit adapter specific identifiers and give the appropriate logical system name in the integration directory...
In ID goto Service Adapter-Specific Identifiers and mention the Logicalsystem and Client and ID...
Check this blog
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
and also
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
for refernece...
Regards,
Sridhar

RFC For IDoc outbound processing

I am creating an RFC for BDC for call transaction we19
input as : idoc number
and output:-.. iDoc Outbound processing done
so:-
I go to we19> give iDoc Number (say, some number for ALEREQ01), and execute> click on Outbound processing-->click enter -->enter
in this way, I can process any iDoc from SAP system to outbound.
I want to create RFC for the same.
Problem:-
when i am executing that RFC, and when I check the iDoc status in we05, that iDoc shows status as Idoc ready to dispatch( its in yellow color).. Its not showing green color and not saying that IDoc passed OK
when I try manually ,I see the status green..OK..successfully
Any idea why I am getting this problem??
Is there any problem in my BDC recording?..but when I run that recording for Process, i dont see any problem,it executes successfully.. but when I copy the Code from BDC and make a RFC using that code, its giving problem as mentioned.

Hi Ankit,
Theorotically it should work.... but I'll suggest not to use BDC here. What you can do is,
1. You have Idoc number..Right?
2. Read control record from EDIDC and data record from EDID4.
3. Then call Master_idoc_distribute.
4. This will again distribute the same IDoc with same control and data record as a new one. It will be same as WE19 , but without WE19.
Please check and confirm.
Regards,
Audy.

IDOC Outbound processing using SAP BC

Hello Experts,
I am trying to develop a simple IDOC outbound processing scenario using SAP BC. In this an IDOC from SAP ECC server will be sent to an external webserver via SAP BC, for this i have done all the setup i.e Establishing connection between SAP BC & SAP ECC, ALE settings, creating a new Routing rule, but when i try to run this scenario, i am getting the following error 'IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE' , is there any way to import the IDOC metadata, just like how we do in SAP XI using IDX2. Please Help...
Thanks & Regards,
Amit Naik

Hi Michal,
Following is the error which i am getting :-
2009-03-12 21:56:59 IST com.sap.conn.idoc.IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "" is unavailable.
     at com.sap.conn.idoc.rt.DefaultIDocDocument.<init>(DefaultIDocDocument.java:132)
     at com.sap.conn.idoc.jco.JCoIDocDocument.<init>(JCoIDocDocument.java:74)
     at com.sap.conn.idoc.jco.JCoIDocDocument.createIDocDocument(JCoIDocDocument.java:117)
     at com.sap.conn.idoc.jco.JCoIDocRuntime.createIDocDocumentList(JCoIDocRuntime.java:83)
     at com.sap.conn.idoc.jco.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:88)
     at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:141)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:2621)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2298)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2130)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2012)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:1903)
     at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:258)
     at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:320)
     at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:219)
     at com.wm.util.TimeWrappingProvider$TimeMesuredTask.run(TimeWrappingProvider.java:40)
     at com.wm.pkg.sap.rfc.ListenerThread.run(ListenerThread.java:70)
Thanks & Regards,
Amit

AES filing error - Idoc Outbound Processing: EDI number cannot be compiled

Hi Gurus,
We are configuring the AES filing.
we've done the EDI configI and initally we got the error that EDI partner is not maintained. As per the suggestions from this Forum we've added the cusoms office details in geography tab.
Now when we are trying to process the same, we are getting the error "Idoc Outbound Processing: EDI number cannot be compiled"
All suggestions are welcome.........
Thanks in Advance.

Hi Shiva,
Here goes the solution: you need to maintain the Number of the Number Ranges starting with "10" and this applies only to GTS system as this is HARD-CODED in the Program, apart from 10 any number of the number range will result in an "EDI Number Range compilation" error.
Cheers
Harsha

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

What is IDOC Inbound process and Outbound Process?

What is IDOC Inbound process and Outbound Process?
can any one explain about the inbound and outbound process step by step?
Tks in advance,
Phanikumar

Hi,
Inbound means transfer legacy data to SAP system and
outbound means transfer SAP system data to legacy system.
Regards,
Prashant

Problems with processing outbound IDocs in background processes

Hello everybody,
I have a question for working with ABAP-PSS Ports.
The behvaiour is that I want to send master data, for example customers, to a function module. This function module works like an converter which process and writes the files in the filesystem.
Following situation:
- I have defined a partner System with different message types, for example DEBMAS and everthing what is necessary to replicate data to partner systems.
- I have defined also a Port like ABAP-PPS Port for calling my own function module.
- If I runs the program I process only 50 Idocs per process because otherwise i can happen that there are to many look entries in the system and the job crashs. (For example all customers are around 50000 Idocs).
Now my problem is that the worker for processing idocs starts each process in the foreground and in parallel.
But this is very strange! Because then all dialog processes are reserved and the system will be very slow!
How can I configure the Port or what have I to implement in my fucntion module to start processing in background (this is the very important point) and maybe allow the program only to use one or two process at the same time?
I have found on the function module EDI_DOCUMENT_CLOSE_PROCESS which I the parameter "Background". What thas this mean? I have set B for this but it has no effect!
Regards
Christian

I know that for inbound interface it is possible to define if in foreground or background and if parallel processing is allowed.
Who knows how I can do this also for outbond?

Green flag: scheduled for outbound processing

We had some network connection problem.Outcome was that in SXI_MONI ,there were some
red color flags,single rectangles,green flags.
Firstly i restarted red color flag,secondly i restarted single rectangles.In this way,first two issues got resolved.
Third problem was "scheduled for outbound processing" ie green flags.
Fo this , i decided to fiest relate how many actual idocs are posted to destination.While i was going with htis activity.
automatically after two hours green flags got processed.
So what does this means ,that green color flag is scheduled to run later and an XI consultant needn;t work on this part ?

Dear sirs,
I feel registrations should be one time activity, ideally speaking.The queue cannot come into picture if it was not registered.
Now i a queue is stuck due to network disconnect( i am referring to only and only network disconnect) here.I do not mean any message mapping failure and i do not mean any udf error or something.
So if a queue is stuck due to a netwrk disconnect,plz guide me witha solution.What i came acroos i just mentioned.
As what u r saying that we need to register/deregister queus.Kindly justify this article then as given in subject.
You may correct spelling of technical.I did so to avoid this site filter.
http://www.saptecnical.com/Tutorials/XI/XMLMessageQueues/Monitor.htm
Edited by: aditya sharma on Jul 26, 2010 3:01 PM

Troubleshoot: How to process messages in "Recorded for Outbound processing"

Dear Experts,
I have File >XI(3.0)>IDoc scenario with 10-25 interfaces. Per interface an average of 200 msges.
Now we have an issue. from past 6 days all the messages for one of the interfaces are in status: "Recorded for Outbound processing"(with that single small black right arrow) in SXMB_MONI(around 1760 till now). Other than this few 100 messages for couple other interfaces are also in same status. There are other message interfaces using the same Idoc type; but they dont have this problem.
I have checked the queues: SMQ1/Q2. There are no errors. The other threads mention about some reports; but all are for error messages. So that also did not help!
On the first day someone had deleted the error queue entry. They had first checked the message in the queues but that was not showing any status. (This is very strange... but for some messages , the left most status column is not showing any status at all.. but while clicking on the end time column; I am getting the pop up which says succesfully processed). But this is not our problem right now.
Please help me process the messages in the "Recorded for Outbound processing" status.. some how!!!
Thanks in advance for your inputs....
P.N: Runtime workbench here is not configured properly. No CC monitoring tab; message monitoring shows only adapter messages etc.... So cannot check anything here

Thank you for your inputs.
@Udo.... SMQR- no issues.
The RFC destination is fine.
@Abhishek The Idoc has not reached SAP. The xml messages in XI are in "Recorded for outbound processing" which is kinda like Scheduled, i think. Anyway I checked the R/3 cant find the messages or errors.
Any help would be highly appreciated....

How to trigger FIDCCP02 idoc for outbound vendor invoices?

Hi
1. How can i trigger the idoc FIDCCP02 for outbound processing? I am trying to use this idoc to send the vendor invoice data to another system.
2. How do i send existing data from sap to another system thru idocs?
pls give me the steps.
Regards
Sujai

Hi Sujai,
First you have to fill the your data into a table which is like the structure of EDIDD.Here you have to fill the all segmetns in the sequence which defined in the idoc type only other wise you will get error 26.
Then pass the control record data in the structure like EDIDC here you have to fill the sender,receiver,partner profile,idoc type message type like stuff.
Then pass these table and structure to the function module MASTER_IDOC_DISTRIBUTE.
Then idoc will created by above funciton module.
If you want pass data in xml format then you have to create xml port in we21 and pass this port name in the EDIDC structure.
Thanks,
radha.

Idoc failure(outbound process)

Similar Messages

Maybe you are looking for