Failure To Post IDoc Into R/3

I have a interface scenario that maps a XML file into a SAP IDoc. When the message reaches the Call Adapter stage I get the following error
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>User is locked. Please notify the person responsible</SAP:P1>
<SAP:P2 />
What I do not know is what User ID is XI using to extract the metadata. Does any body know?
If I go to transaction IDX2 and try and manual create the metadata I get the same error message.
Regards,
Simon

I have fixed the problem. SAP XI was using the wrong port (IDX1). I have reduced the number of ports to one per SAP R/3 system.
Now the metadata is loaded into cache when an IDoc is posted into SAP R/3.
Thanks fot your answers.
Regards,
Simon

Similar Messages

Posting IDocs into the same system

Hello Experts,
We are having a requirement where-in we have to created a IDoc for the failed message in our RFC and hence it should be created in our own system and should be having status Error (Red).
Is there any function module by which we can create the IDocs without specifying the receiver port. We tried debugging MASTER_IDOC_DISTRIBUTE FM at IDOC_CREATE_ON_DATABASE but it also expects the receiver information.
Thanks in advance.
regards
rajeev

No we haven't specified dummy partner. so we have to create a partner profile with the dummy receiver? And what port we should specify? Should it point to the same RFC destination?
regards
rajeev

How to post idoc from r/3 to xi

hi experts i have one doubt abt posting idoc from r/3 to xi
how to post
for vendor master idoc
for sales order idoc
for purchase order idoc
for delivery idoc
is there any inbuilt posting prgms r there or we have to write the prms.
please clear me
regards
babu

to add more...
Befor posting IDOCS into XI..we need to do ALE SETTINGS...as fallows..
ALE settings.
SAP XI1) RFC Destination (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.
2) Create Port (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 (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (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.
2) Create Port (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)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (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.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.
and coming to the posting, u can go with WE19

Unable to import IDoc into IR

Hi - For no reason i can't import the IDoc into XI.
The problem seems to be that in backend system is a problem. The basis-type and the segments are all released - to me because i released and de-released them. The Idoc was developed in client 010 and i want to import ist from 011 - of course there was some kind of transport!
In WE20 of backend system i am not able to pick this IDoc for Incoming parameter, no idea why.
In XI i am able to import MetaData via IDX2 but i am still not able to import the IDoc!!
can somebody help?! br Jens

Hi,
1 Scenario
This guide deals with all the configurations required to create an IDoc adapter in Exchange Infrastructure
3.0 to send an IDoc from XI to the SAP backend system.
Unlike other types of adapters, the IDoc adapter has dependencies on the XI 3.0 ABAP configurations and
the backend SAP system configurations. Those configurations information will have to be either created
first or retrieved in order to complete the IDoc adapter configuration.
2 Introduction
Configuring IDoc adapter in Exchange Infrastructure 3.0 requires some configuration on the SAP
systems, for both XI and the backend system where the IDoc message is to be sent. These steps, although
simple, are many times missed or mis-configured, causing the delivery of messages to fail.
Since IDoc adapter uses the ABAP stack, instead of J2EE, the configuration requirements are mainly in
ABAP.
Setting up IDoc adapters requires the XI integration server to be able to communicate with the backend
SAP system, and also to make sure that the Logical System Name used when posting IDoc exists on the
backend SAP system.
3 The Step By Step Solution
The basic steps for the IDoc configuration are outline below:
1. Configure SM59 on XI to communicate to SAP backend system.
2. Configure port on XI for IDoc communication.
3. Create or verify the Logical System Name on the SAP backend system.
4. Create or verify business system in XIs System Landscape Directory.
5. Verify the Logical System Name of the business system.
6. Verify or add the Logical System Name for the sender business system.
7. Create/configure the Communication Channel for the IDoc receiver adapter
3.1 Configure SM59 on XI to communicate to SAP backend system.
1. Using transaction SM59, create an RFC destination with Connection Type = 3.
In this example, the RFC destination name is NDVCLNT510.
2. Enter the logon information:
3. Test the connection by clicking on Testing connection and Remote logon.
Both must be successful.
3.2 Configure port on XI for IDoc communication.
4. Go to transaction IDX1 on XI, and create a port. In this example, the Port name is SAPNDV.
     The Port name must be in the form of SAPxxx, where xxx is the system ID of the backend SAP
system.
     The Client must be the client number of the backend SAP system.
     Select the RFC Destination which was created in the previous step.
3.3 Create or verify the Logical System Name on the SAP backend system.
5. Enter transaction SALE on the SAP backend system.
6. Create or verify the Logical System Name. In our example, NDVCLNT510 is verified.
3.4 Create or verify business system in XIs System Landscape Directory.
The business system name for the SAP backend system must contain a valid Logical System Name. This Logical System Name is the one verified or created in the previous step.
7. In the System Landscape Directory, select the SAP backend business system. If one does not exist, then create the business system. Verify the Logical System Name.
3.5 Verify the Logical System Name of the business system.
8. In the Integration Directory, doubleclick on the business system (in our example, it is NDVCLNT510).
Navigate the menu:
Service Adapter Specific Identifiers.
If information is empty or incorrect, then it will have to be synchronized with the content of the System Landscape Directory. Follow the steps below for synchronization.
9. (Optional) Synchronization of the business system in Integration Directory to the business system in System
Landscape Directory.
     Double-click on the business system in the Integration Directory.
     Switch to Edit mode.
     Select menu: Service Adapter-Specific Identifiers
10. (Optional) Within the dialog box, click on the button as indicated below to resynchronize.
11. (Optional) If the expected data from the System Landscape Directory is not updated, then the SLD cache may need to be cleared first.
3.7 Create/configure the Communication Channel for the IDoc receiver adapter.
15. In the Integration Directory, create an IDoc receiver communication channel.
     The RFC Destination is from step 3.1.
     The Port is from step 3.2.
NOTE:
There is no need to create an IDoc sender Communication Channel for XI. Instead, the backend SAP system must be configure to send the IDoc to XI.
4 Appendix
Transaction: IDX2
There are a couple of situation where IDX2 can be useful on the XI system.
1. When we want to test connection between the XI and SAP backend system.
2. When an IDoc has changed, and the meta data stored in XI needs to be update. When an IDoc is sent from the SAP backend system to XI, XI will first check to see if the meta data for the IDoc is already in its persistent cache. If not, then XI will use the configuration in IDX1 to retrieve the IDoc meta data from the backend system. If the
meta is already in cache, then it will NOT do so. Therefore, when an IDoc has changed, it is necessary to manually update the new meta data on XI, or delete it from the cache, so that the latest version can be retrieved. IDX2 is used for this purpose.
Go to transaction IDX2 and click on Create.
Enter the IDoc Type and the Source Port as defined in step #2. Click Continue.If successful, the following will show up. If error occurs, then the IDX1 configurations will need to be re-checked.
Regards
Hemant
Award point if find helpful

Authorization error in posting IDoc

Hi,
I have completed configuration of File to IDoc scenario. When File adapter has picked up the file from FTP server, the message is processed with outbound error.
To find out the error occured at the outbound side, I ran the transaction 'SM58' which explained that XIAFUSER does not have authorizations to post the IDoc to destination system. Can somebody provide what authorizations should be given to this user to facilitate the processing of message.
In another instance the same error has resulted but notifying the different user. This time WF-BATCH does not have authorizations to post the IDoc to destination system.
As per my understanding there should be some system configuration where you have an option of specifying the user for posting IDocs to destination system.
Please confirm whether my understanding is correct and also let me know the where it is done?
Regards,
Suraj

Hi Suraj,
The user id which you are using in your RFC destination will be of your target system to login. This user id should be having all SAP_ALL authorizations attached into their profile.
Pls do try with the help of your basis by assigning this profile to your WF-BATCH user.
Cheers
JK

Breaking up of, One IDoc to many IDocs & combing Many IDocs into one IDoc?

Does anybody have any sample code of:
Splitting an IDoc into multiple IDocs and
Combining many similar IDocs into one IDoc
Any pointers will be appreciated.
Regards
Mahesh

This is the code for splitting of an inbound idoc into multiple idoc
REPORT ztemp no standard page heading .
******************Data Declaration for selection screen***************
TABLES: edidc,edidd.
CALL SELECTION-SCREEN 9000.
SELECTION-SCREEN: BEGIN OF SCREEN 9000,
 BEGIN OF BLOCK b1 WITH FRAME.
SELECT-OPTIONS: idocno FOR edidc-docnum.
SELECTION-SCREEN:END OF BLOCK b1 ,
 END OF SCREEN 9000.
*******************Data Declaration ************************************
DATA : it_contrl LIKE TABLE OF edidc WITH HEADER LINE,
 it_hdata LIKE TABLE OF edidd WITH HEADER LINE,
 it_fdata LIKE TABLE OF edidd WITH HEADER LINE,
 it_gdata LIKE TABLE OF edidd WITH HEADER LINE,
 it_data LIKE TABLE OF edidd WITH HEADER LINE,
 it_status LIKE TABLE OF bdidocstat WITH HEADER LINE,
 it_bdwfretvar LIKE TABLE OF bdwfretvar WITH HEADER LINE,
 it_bdi_ser LIKE TABLE OF bdi_ser WITH HEADER LINE,
 it_ldata LIKE TABLE OF edidd WITH HEADER LINE,
 it_tede2 LIKE tede2,
 vbeln LIKE vbak-vbeln,
 idocnum LIKE edidc-docnum,
 result LIKE bdwfap_par-result,
 it_stat LIKE edids.
DATA : count TYPE i ,
 counter TYPE i ,
 temp TYPE i VALUE 1 ,
 line TYPE i ,
 tab LIKE sy-tabix.
*********************passing values to control record*****************
it_contrl-direct = '2'.
it_contrl-rcvprn = 'ID3IDES802'.
it_contrl-rcvprt = 'LS'.
it_contrl-doctyp = 'ORDERS05'.
it_contrl-idoctp = 'ORDERS05'.
it_contrl-sndpor = 'ZSOFI'.
it_contrl-sndprt = 'LI'.
it_contrl-sndprn = '1000'.
it_contrl-mestyp = 'ORDERS'.
APPEND it_contrl.
************************Select query for data*************************
SELECT * FROM edid4 INTO CORRESPONDING FIELDS OF TABLE it_fdata
WHERE docnum IN idocno.
SELECT * FROM edid4 INTO CORRESPONDING FIELDS OF TABLE it_data
WHERE docnum IN idocno AND segnam NOT LIKE 'E1EDP%' .
SELECT * FROM edid4 INTO CORRESPONDING FIELDS OF TABLE it_hdata
WHERE docnum IN idocno AND segnam LIKE 'E1EDP%'.
**************select query to count the no of E1EDP01 segment*********
SELECT COUNT( * ) FROM edid4 INTO count WHERE docnum IN idocno AND
segnam = 'E1EDP01'.
*************to determine the no of idocs to be generated************
count = count / 5.
PERFORM datasplit.
**********************************for remaining idocs*****************
counter = count MOD 5.
IF counter NE 0.
PERFORM dataremain. .
ENDIF.
*& Form datasplit
 text
--> p1 text
<-- p2 text
FORM datasplit .
LOOP AT it_data.
 MOVE-CORRESPONDING it_data TO it_gdata.
 APPEND it_gdata.
ENDLOOP.
DO count TIMES.
 PERFORM split.
 perform idoccreate.
 enddo.
ENDFORM. " datasplit
*& Form SPLIT
 text
--> p1 text
<-- p2 text
FORM split .
LOOP AT it_hdata.
 IF temp <= 5.
 ON CHANGE OF it_hdata-segnam.
 IF it_hdata-segnam = 'E1EDP01'.
 MOVE-CORRESPONDING it_hdata TO it_gdata.
 APPEND it_gdata.
 ELSE.
 MOVE-CORRESPONDING it_hdata TO it_gdata.
 APPEND it_gdata.
 temp = temp + 1.
 ENDIF.
 ENDON.
 ENDIF.
ENDLOOP.
ENDFORM. " SPLIT
*& Form dataremain
 text
--> p1 text
<-- p2 text
FORM dataremain .
CLEAR it_gdata[].
LOOP AT it_data.
 MOVE-CORRESPONDING it_data TO it_gdata.
 APPEND it_gdata.
ENDLOOP.
LOOP AT it_hdata .
 IF sy-tabix > 10.
 MOVE-CORRESPONDING it_hdata TO it_gdata.
 APPEND it_gdata.
 ENDIF.
ENDLOOP.
perform idoccreate.
ENDFORM. " dataremain
*& Form idoccreate
 text
--> p1 text
<-- p2 text
form idoccreate .
***********************for creating the inbound idocs****************
CALL FUNCTION 'IDOC_INBOUND_WRITE_TO_DB'
 EXPORTING
 pi_status_message = it_stat
 pi_do_handle_error = 'X'
 PI_NO_DEQUEUE = ' '
 pi_return_data_flag = 'X'
PI_RFC_MULTI_CP = ' '
 IMPORTING
 pe_idoc_number = idocnum
 pe_state_of_processing = sy-subrc
 pe_inbound_process_data = it_tede2 "for process code
 TABLES
 t_data_records = it_gdata
T_LINKED_OBJECTS =
 CHANGING
 pc_control_record = it_contrl
EXCEPTIONS
 IDOC_NOT_SAVED = 1
 OTHERS = 2
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
COMMIT WORK.
*it_contrl-status = '64'.
modify it_contrl index 1.
****************for posting the idoc**************************
CALL FUNCTION 'IDOC_INPUT_ORDERS'
 EXPORTING
 input_method = 'A'
 mass_processing = '1'
 IMPORTING
 workflow_result = result
APPLICATION_VARIABLE =
IN_UPDATE_TASK =
CALL_TRANSACTION_DONE =
 DOCUMENT_NUMBER = vbeln
 TABLES
 idoc_contrl = it_contrl[]
 idoc_data = it_gdata[]
 idoc_status = it_status[]
 return_variables = it_bdwfretvar[]
 serialization_info = it_bdi_ser[]
EDI_TEXT =
EDI_TEXT_LINES =
 CLEAR : it_contrl-docnum.
COMMIT WORK.
endform. " idoccreate

Error 51 when posting IDOC to SD

Hello All,
We are changing our EDI translator which had a SAP extension automatically process the IDocs into SAP using ALE process.
I'm testing the new procedure scheduling a job to run RSEINB00.
The error I'm getting is (51 enter a numeric value) when posting an order in SD.
IDocs are created with the follow status.
50 - IDoc added
64 - IDoc ready to be transferred to application
62 - Direct call started
51 - enter a numeric value.
On the partner profile is set-up as Message type ORDERS process code ORDE and processing by function module is set to trigger immediately.
Is there something I'm missing?
I can get around this by reprocess the IDocs using BD87 Process Inbound IDocs' the orders are created.
This would be a manual process and something I do not want to do.
Please Help
Joan

Hi Nandu,
I'm not sure how to run BD87 in foreground mode. I did run BD87 using the debug mode.
The error is No batch input data for screen && - SAPM55430121 - Message no. 00344 and the diagnosis were:
The transaction sent a screen that was not expected in the batch input session and which therefore could not be supplied with data. The transaction behaves differently in background processing in a batch work process than when running in dialog (SY-BATCH is queried and changes the screen sequence).
I ran the same idoc using BD87 without the debug and it was posted.
I do not want to use transaction BD87 when we go live.
Is there a config that I needs to set up?
Is there something in the control record I'm missing?
Joan

SM 56 error while posting IDOC thru XI (File to IDOC) ????

Hi ,
When I am trying to post data into R/3 system thru MATMAS idoc,I have problem in posting data in R/3 system. In XI side the message is sent correctly to R/3 system, but in R/3 it is giving me SM 56 error, while mapping I tried to map only few fields, other mandatory fields I had populated with some constants and values and rest unwanted segments I disabled them. When I saw in error log it says PARTNER PROFILE is not properly set (but I checked Partner Profile is correct), when I checked the record it shows all fields (mapped with constants and values) except the mapped fields.
Can anyone help me in this as I am struggling like anything...
Thanks in advance
Andy

hi Andy,
if you have a problem with control record have a look
at my weblog:
/people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI FAQ - Frequently Asked Questions</a>

Splitting single idoc into multiple xml's

Hello,
My requirement is such that, i need to split an custom IDoc into three xml which will be picked up by MDM, as i am new to PI 7.1 kindly guide me through the process.
and the second requirement is, i need to map the same custom IDoc into three different MDM repositories pls guide me through the process

Hi Abhishek,
[quote]My requirement is such that, i need to split an custom IDoc into three xml which will be picked up by MDM, as i am new to PI 7.1 kindly guide me through the process
For this, you have to go for multimapping.
The links for it are already provided in the above posts.
and the second requirement is, i need to map the same custom IDoc into three different MDM repositories pls guide me through the process
Can you please explain this requirement further?
-Supriya.

Conversion of inbound IDOC into XML file

Hi experts,
We have an inbound idoc (FIDCC2) that starts and triggers the creation of an FI document. We would like now, that, instead of creating the FI document, the inbound IDOC creates an XML file on a given directory, with the contents of the idoc. Can anybody explain how to configure this?
Many thanks in advance,
John De Coninck.

John,
Firstly, need more information. If I understand you correctly, you are getting an inbound FI document that is created as an IDOC and it posts into FI (using an underlying FM/transaction etc). Now you want to convert this IDOC into XML on a folder (which can be found on AL11 (a.k.a App Server)).
Question 1: Where are you getting this IDOC from? Is it through EDI/ALE? What is your interfacing server (the one that is sending you this IDOC.
Question 2: What format is this IDOC coming in? Is it flat/XML etc?
Question 3: Is this an internally created IDOC? Is there an attached partner profile in WE20? If there is a partner profile that exists and you're using this to create the inbound IDOC, then there are process codes available to forward these IDOC's (e.g ED08).
There are many ways you can achieve this but everything depends on how your system is configured and how this processing is going on.

Error Posting IDOC: need help in understanding the following error

Hi ALL
Can you please, help me understand the following error encountered while the message was trying to post a IDOC.
where SAP_050 is the RFC destination created to post IDOCs
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>FM NLS_GET_LANGU_CP_TAB: Could not determine code page with SAP_050 Operation successfully executed FM NLS_GET_LANGU_CP_TAB</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: FM NLS_GET_LANGU_CP_TAB: Could not determine code page with SAP_050 Operation successfully executed FM NLS_GET_LANGU_CP_TAB</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Your help is greatly appreciated.............Thank you!

Hi Patrick,
Check the authorizations assigned to the user which you used in the RFC destinations, If there is no enough authorizations then it is not possible to post the idocs.
Also Refer this Note 747322
Regards,
Prakash

Getting Error while posting billing into accounting.

Hi All,
Could any one help on this error,i am getting this while posting billing into accounting.
Tax statement item missing for tax code O0
Message no. FF805
Diagnosis
No tax item exists for tax code O0 in a G/L account item. A possible cause is an incorrect transfer of parameters by the application to the Accounting interface.
Procedure
Enter an OSS message.

Hi Raja,
We have many FF805 errors reported by customers and the same solution
has resolved the problem. Please note that the SD-FI interface changed
from earlier releases.
In the vast majority of cases, error FF805 occurs because of an error
in your pricing procedure. The previously attached note 112609 explains
in detail how tax codes are transfered to conditions.
The note 400766 explains the checks performed by the system on the Tax
codes:
1. system checks whether there is a revenue line for each tax line.
2. in the reverse case, for each revenue line containing a certain
   tax indicator there must be a tax line with this indicator.
If the tax condition has condition value zero and condition base
value zero, then it is not transferred to FI.
If you have revenue lines containing a tax indicator XX, but no
tax line with tax indicator XX, then the error FF805 issues, and
it is justified. => Please check these informations. I have attached
notes for further information.
-> EXAMPLE
   If tax condition MWST has base amount zero and value zero; for this
   reason it is not passed to accounting. But, according to the
   criteria reported by note 112609, its tax indicator EG: A7
   has been assigned to the condition EG: ZBR1.
   So in accounting there would be a revenue line with tax indicator A7,
   but there isn't any tax line with indicator A7 (because MWST doesn't
   pass to FI). The note 400766 states situation is unallowed, and error
   FF805 is justified.
Thanks and best regards,
Smile

I paid $20 to upgrade my iPod touch and it didn't go through for me. The person who assisted me said that if it didn't work out that I would get my $20 posted back into my credit card. Prior to this service I made a purchase from the iTunes Store.

I paid $20 to a person from the apple customer support line to have my iPod touch upgraded but it never went down. The representative who assisted me said that I would have those $20 posted back into my Visa card if it didn't go through. The service never got to happen and failed. Prior to this I made a purchase from the iTunes Store for $7.00, which they never billed me. So until I pay for the previous iTunes purchase, I am not allowed to download any applications. This is the reason why I need the $20 back from the separate request I made with apple which never worked out. Cause as soon as I pay for the previous iTunes purchase that I made apart from apple, then I could once again start to download and install applications. I have a week already without downloading apps. Please refund my money back a.s.a.p.

Not sure what this is all about...
JamesAbreu55 wrote:
I paid $20 to a person from the apple customer support line to have my iPod touch upgraded but it never went down. ...
However... This is a user to User Forum.
To Contact iTunes Customer Service and request assistance
Use this Link > Apple Support iTunes Store Contact

Unable to import IDoc into NWBPM from NWDS

Dear PO Experts,
We are migrating an existing interface
(IDoc<-->PI<-->SOAP using BPM (Multiple sync calls)).
We are un able to import IDoc into NW BPM project as a service Interface. (For BPM we exported IDoc into local system as an external definition and did few modifications to the xsd as per below blog and exported back to PO server as an external definition.Create Service Interface for the same .
http://scn.sap.com/community/process-orchestration/blog/2014/09/24/idoc-to-nw-bpm-scenario#comment-542653 )
We are getting below exception while importing IDoc Service Interface into BPM project.I have attached IDoc WSDL file for your reference.Could you please share your expertise on this issue.
>>>An internal error occurred during: "Importing MOIN models for XSDs and WSDLs...".
java.lang.OutOfMemoryError: Java heap space
at java.util.ArrayList.<init>(ArrayList.java:112)
at org.eclipse.xsd.impl.XSDParticleImpl$XSDNFA.initialize
(XSDParticleImpl.java:1271)
at org.eclipse.xsd.impl.XSDParticleImpl$XSDNFA.<init>
(XSDParticleImpl.java:1050)
at org.eclipse.xsd.impl.XSDParticleImpl$XSDNFA.initialize
(XSDParticleImpl.java:1149)
at org.eclipse.xsd.impl.XSDParticleImpl$XSDNFA.<init>
(XSDParticleImpl.java:1039)
at org.eclipse.xsd.impl.XSDParticleImpl$XSDNFA.initialize
(XSDParticleImpl.java:1272)
at org.eclipse.xsd.impl.XSDParticleImpl$XSDNFA.<init>
(XSDParticleImpl.java:1060)
at org.eclipse.xsd.impl.XSDParticleImpl.getDFA
(XSDParticleImpl.java:2041)
at org.eclipse.xsd.impl.XSDModelGroupImpl.validateRoot
(XSDModelGroupImpl.java:599)
at org.eclipse.xsd.impl.XSDComplexTypeDefinitionImpl.validate
(XSDComplexTypeDefinitionImpl.java:1408)
at org.eclipse.xsd.impl.XSDConcreteComponentImpl.validate
(XSDConcreteComponentImpl.java:565)
at org.eclipse.xsd.impl.XSDSchemaImpl.validate(XSDSchemaImpl.java:1653)
at com.sap.tc.esmp.tools.core.util.EMFUtils.validate(EMFUtils.java:613)
at
com.sap.tc.esmp.tools.xsd.xml.EmfSchemaImporter.calculateAffectedPartitions(EmfSchemaImporter.java:903)
at
com.sap.tc.esmp.tools.wsdl1import.Wsdl1Importer$ImportChain.calculateAffectedPartitions(Wsdl1Importer.java:365)
at
com.sap.tc.esmp.tools.wsdl1import.Wsdl1Importer$ImportChain.resolveImportLink(Wsdl1Importer.java:545)
at
com.sap.tc.esmp.tools.wsdl1import.Wsdl1Importer$ImportChain.createChainLink(Wsdl1Importer.java:522)
at com.sap.tc.esmp.tools.wsdl1import.Wsdl1Importer$ImportChain.init
(Wsdl1Importer.java:461)
at com.sap.tc.esmp.tools.wsdl1import.Wsdl1Importer$ImportChain.<init>
(Wsdl1Importer.java:337)
at com.sap.tc.esmp.tools.wsdl1import.Wsdl1Importer.prepareWsdlImport
(Wsdl1Importer.java:1381)
at com.sap.tc.esmp.tools.wsdl1import.Wsdl1Importer.prepareWsdlImport
(Wsdl1Importer.java:1368)
at com.sap.tc.esmp.tools.facade.Import.prepareWsdlImport
(Import.java:106)
at
com.sap.tc.esmp.tools.editor.jobs.RepositoryMetadataProcessor.doImportFiles(RepositoryMetadataProcessor.java:298)
at
com.sap.tc.esmp.tools.editor.jobs.RepositoryMetadataProcessor.access$300(RepositoryMetadataProcessor.java:52)
at com.sap.tc.esmp.tools.editor.jobs.RepositoryMetadataProcessor$4.run
(RepositoryMetadataProcessor.java:248)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Regards
Venkat

Hi Venkat,
Find the below link.
http://scn.sap.com/community/process-orchestration/blog/2014/11/29/using-idocs-in-nwbpm

TCODE TO DOWNLOAD IDOC INTO A FLAT FILE

Hi All,
Please let me know if there is any tcode to download IDOC into a flat file..
Regards,
Kaveri

try with we60 where you should have links to download the idoc type.
Please check this:
1. How to Download a Hierarchy to a Flat File
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/0403a990-0201-0010-38b3-e1fc442848cb
2. How To Convert an IDoc-XML structure to a flat file and vice versa in XI 3.0 Version 1.10
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
run the report RSEOUT00 with the idoc number, flat xml file will be generated at the location user/sap/XI/SYS/global/idoc_file
Please rewrds if found help ful

Failure To Post IDoc Into R/3

Similar Messages

Maybe you are looking for