Error in Idoc to XML conversion

Hi,
I am doing Idoc to XML conversion using standard program RSEINB00. Can anyone plz tell me what are the pre-requisites to executing this program? I am getting an error message Port XXX segment defn YYYYY in IDoc type ZZZZZ CIM type do not exist.
Why am i getting this error? and what is the slution for it?
Regards,
Mateen.

Hi
Delete the metadata in IDX2 for the corresponding IDOC type in PI.
Also re-import the same in IDX2.
Reimport the IDOC type into Integration Repository under your SWCV.
Then check it..
Refresh the cache also.

Similar Messages

Mapping error in FCC to XML conversion

hiii friends,
im donig a simple fcc to xml conversion
my Sender msg type is like
TXT_mt
      records                             1.1
            row                             1.n
                id                             1
                Name                       1
                address                   1
My receiver msg type like
Xml_mt
      records                             1.1
            row                             1.n
                id                             1
                Name                       1
                address                   1
msg mapping like
records--->records
id--->id
Name-->Name
address-->address
**Im getting a mapping error like**
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_pepsi_fcc_file_mm_</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
<SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>During the application mapping com/sap/xi/tf/_pepsi_fcc_file_mm_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I ve checked my adapeters they r green.
Could u tell me the problem here and how to solve it???
Regards
Balaji

Hii Volker,
I have tried to understand the trace msg,. i got one interesting error message i hope it will tell the exact problem im facing,,,
<Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_pepsi_fcc_file_mm_</Trace>
<Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns:xml_mt/record/row. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram
My Sender CC contains the following FCC parameters
Document Name -
> txt_mt
Recordset Name -
> records
recordset Structure -
> row, *
row.fieldNames -
> id, Names,address
row.fieldSeparator -
> , (comma)
row.endSeparator--- > 'nl'
row.processConfiguration -
> FromConfiguration
my TXT_in.txt contain
100,balaji,chennai
200,raj,orissa
300,charakrat,bangalore
Regards,
Balaji
Edited by: Balaji Pichaimuthu on Jul 1, 2009 3:44 PM

IDOC to XML Conversion

Hi ABAPers,
Is there any standard procedure to convert IDOC's to XML format ? If
yes can anyone please help me the procedure or steps how to achieve
this conversion.
Regards
VEnk@

HI Gautham,
Your answer was helpful.
I am trying to use IDOC_XML_Translate.
Here if you can see the source code of the function module
at the end data is holding by STR and transformed and passed into screen number 100.
But i am trying to download the file so i have created a ZFunModule and in source code
i have used GUI_DOWNLOAD here the problem in STR is string not a table, so how to pass the STR data to Internal table.
Transformation
CALL METHOD idoc->get_xmldata_as_string
    IMPORTING
      data_string = str.
CALL SCREEN 100.
CALL FUNCTION 'GUI_DOWNLOAD'
EXPORTING
    filename = 'C:\Venkat\venkat.xml'
tables
    data_tab = ?
Are you having any solution for this ? If yes please share.
Regards
VEnk@

Regarding outbound idoc into xml conversion

Hello everyone
can anyone let me kno all the procedure to make our idoc outbound and convert it into XML file, is there any standard program or any other method if i am using we21 then what thing i have to do. is it neccesary for us to go to tc we60 and change schema of our structure or not, i don't want to use XI, please tell me whole procedure if possible, waiting for your reply.
plz reply me.
Thanks & Regards
vimarsh b
Edited by: vimarsh b on Jan 8, 2008 5:58 AM

hai,
check this.
Outbound Interface
PROCESS DIAGRAM for Outbound Interface
1. Analyse Hierarchy Levels
2. Create New segment
3. Create New IDoc Type
4. Create New Message Type
5. Link Message with IDoc Type
6. Create an entry in EDP13 via transactions WE20 and BD64
7. Populate the Custom IDoc via ABAP Program
7b Error Handling
7c. Send Status Email
8. Test the Population of the Custom IDoc
Step 1 Analyse Hierarchy Levels:
Analyse the data relationships being processed in the interface. Define the appropriate hierarchical Parent-to-Child relationships.
Navigate to transaction code WEDI
Transaction WEDI displays the IDOC main menu. This allows navigation around the various development and control areas to create a customised IDOC.
Step 2 Create a new segment:
via wedi : Development - IDOC Segments or Transaction code WE31.
Enter segment name and click on Create.
? The name of the segment type must start with Z1 , and have a maximum of eight characters.
Enter description and enter the relevant field names and data elements.
? The segment should represent a structure in the program so for each field in the segment a field name and a data element must be defined.
Save the segment and enter Person Responsible and Processing Person .
Go to Edit and Set Release.
Repeat this procedure for each new Segment in the IDOC.
Step 3 Create a new IDOC Type
via wedi Development - IDOC Types or Transaction WE30.
Enter segment name (starting with Z), click on Basic Type and then Create.
Create as new, enter Person Responsible and Processing Person and enter description.
On Create Basic Type screen decide where segments should be inserted and go to Edit/Create Segment.
Complete relevant fields in the Maintain Attributes screen:
From the relevant segments created in Step 2 enter the Segment type and if mandatory segment.
The Minimum and Maximum number of segments to be allowed in the sequence. (One minimum and one maximum if segment is mandatory).
The Parent Segment and Hierarchy Level will be automatically created depending on where in the IDOC tree you decided to create that particular segment.
Repeat this process for each segment needed in the IDOC type, deciding whether to add the next segments at the same level or as a Child.
When IDOC created return to initial screen. Go to Edit and Set Release.
Go to Transaction WE60 to view the IDoc Type you have created.
Step 4 Create new Message Type
via wedi Development - Message Types or Transaction WE81.
Display/Change and click on New Entries
Create a new Message Type and Save.
Step 5 Link Message Type to IDOC Type
via wedi Development - IDOC Type/Message or Transaction WE82.
Display/Change and then click on New Entries.
Enter Message Type, Basic Type (IDOC Type) and Release (46C) and Save.
Step 6 Create an entry in EDP13 via transactions WE20 and BD64.
The partner profile for the Idoc must be set up and generated in the transaction BD64 and transaction WE20.
WE20 Add Message Type to appropriate Partner Type, Enter Message Type, Receiver Port and Idoc Type and Save.
BD64 Create a Model View, Enter Sender and Receiver Ports, Attach Message Type. Go to Environment on Menu and click on Generate Partner Profiles and generate (not save) profile.
Step 7 Populate the custom IDOC via ABAP Program
See Test Program ZOUTBD_IDOC_TEMPLATE, Appendix IV.
Create an Internal Table for each segment type, this should be exactly the same structure as the segment type.
The control record is filled into a structure like EDIDC. The message type and the Idoc type for the Idoc must be populated into the eddic structure.
- PERFORM populate_Control_structure USING c_mestyp
c_SEGMENT_type1.
The data segments are filled into a structure like edidd-sdata; sdata and the segment name are populated into the edidd structure.
- PERFORM transfer_Parent_data_to_seg.
The standard SAP function module MASTER_IDOC_DISTRIBUTE is called to pass the populated IDOC to the ALE Layer.
- PERFORM master_idoc_distribute.
NOTE: This function module is only called for stand alone programs and Shared Master Data programs (SMD). It is not called when using extensions or output determination.
The ALE Layer handles the sending of the IDOC to the receiving system.
Error Handling (see Step 7b).
Commit work.
Project Specific
Step 7b Error Handling Analyse which fields in the interface are mandatory for the receiving system and who needs to receive error notification.
Declare a structure of type MCMAILOBJ for sending instructions.
Enter values for the internal table based on structure MCMAILOBJ
For selection processes, on SY-SUBRC checks and where fields are mandatory for the receiving system; insert Function Module MC_SEND_MAIL.
Enter values in the following parameters: -
MS_MAIL_SENDMODE = B (Batch Mode)
MS_MAIL_TITLE = 'Mail Title'
MS_MAIL_DESCRIPTION = Error description (e.g. MATNR not given)
MS_MAIL_RECEIVER = Name of Receiver (To be determined)
MS_MAIL_EXPRESS = E (Express Delivery)
MS_MAIL_DLINAME = Leave Blank
MS_MAIL_LANGU = 'E' (Language)
MS_MAIL_FUNKOBJ_NAME = Leave Blank
TABLES
MS_MAIL_CONT = I_MCMAILOBJ
Note:
It has to be determined separately for each interface how these errors and mail notifications are to be grouped dependant upon the number of errors that are potentially likely. One possible approach is to send an email for each reason for rejection and include all the records that failed for that reason in the mail notification. Another possible approach is to send an email for every failure.
When error checking for mandatory fields it is common SAP practice to reject a record on its first failure (irrespective of subsequent errors in that record)
Step 7c Send status mail
Append to table I_MCMAILOBJ details of the time the interface was processed, how many Idocs were created and how many of these produced a status of 03.
Select the user to receive the mail from ZINT_RECEIVER, using the name of the program as a key (SY-CPROG).
Use function Module MC_SEND_MAIL to send a mail to the user containing the contents of I_MCMAILOBJ at the end of the interface processing.
Step 8 Test the population of the custom IDOC
via wedi IDoc - Display IDoc or Transaction WE02.
Enter your message type and execute.
Status should be green, double click on one of the Idocs you have created to view its contents.
If a problem has occurred click on Status which will give you a description of the error.
Drop down Data Records arrow and this should list the data in the IDoc in the correct hierarchical structure.
Click on each individual segment and view the content to check that the correct data has been read.
If you have UNIX access by using AL11 you can view the file that you have created.
Note:
For some interfaces it may be valid to send an empty file to SAP. This empty file is converted to the custom IDOC format expected by SAP. This custom IDOC will contain dummy information. In the inbound processing code, if the dummy information is identified then the processing of the IDOC is considered to be complete and the IDOC should then be assigned a successfully processed status of 53, even though it has not been processed at all.
also gothroughthe links,
http://www.theobald-software.com/download/ERPConnect/ERPConnectDevGuide_EN.pdf.
http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a611c507d11d18ee90000e8366fc2/frameset.htm
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
With regards,
Sowjanya.B.

IDOC to XML : error in opening the output file in iexplorer

Hi Frnds,
I have a scenario IDoc to xml where in Im getting some non ascii values in the idoc for which I used ISO-8859-1 encoding technique but still the conversion is not done. Iam unable to opend the output file in internet explorer giving the follwoing error as :
An invalid character was found in text content. Error processing resource
Please help me how to overcome this issue.
Thanks in advance,

Hi,
As i posted previously in xi UTF-8 is the default encoding if message protocal is FILE.
And UTF-8 encoding support unicodes..
Can reconfigure your receiver file adapter with file type as Binary and check once again.
go through http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/frameset.htm
refer File Type
now i check with a japanese double byte character and i can open in iexplorer.
regards,
pradeep A.

Seeburger EDI Text to EDI XML conversion failure should throw an error

Hi,
I am expecting an error message to be thrown when EDI Text to EDI XML conversion fails at Message splitter of Seeburger module. I am getting the following error in the log.
"2012-01-19T01:46:08.032-0800 ERROR [Error:ID=2150;LEVEL=3] counter value (41) of incoming field (UNB.UNH.UNT:0074) doesnt match the calculated value (39).
DESCRIPTION: Either the counter value is not filled in the source file or the counter field value is wrong. "
But my expectation is that the channel should show some error in Adapter Engine monitoring itself. As shown below, it is just showing some warning that because of above error, it is not creating the attachment. Now I am expecting the the following warning to be an error rather than just warning. Please let me know if any idea on the same.
19.01.2012 01:46:08 Information SEEBURGER/MESSAGESPLITTER: Trying to establish CCI Connection to Message Splitter Adapter
19.01.2012 01:46:08 Information SEEBURGER/MESSAGESPLITTER: Creating CCI Interaction
19.01.2012 01:46:08 Warning SEEBURGER/MESSAGESPLITTER: There is no attachment to split. So there is nothing to do.
19.01.2012 01:46:08 Information SEEBURGER/MESSAGESPLITTER: Finished splitting!
BR,
Aman

Thanks you all for your inputs..
I got the solution for the same.
I need to set the mapping program name specifically rather than AUTO for bic mappingName parameter. This has turned my communication channel status in RWB into Red for errors.
Closing this thread ...
Regards,
Aman

Conversion of IDOC to XML

How Can i convert Conversion of IDOC to XML?
Any code available.

Hi,
Use function module 'idoc_xml_transform' .
U can use transaction 'WE60' to convert it.
convert IDOC data to XML format.
best Regards,
Brijesh

ResultSet XML Conversion Error

Hi,
BPEL, SOA 11g, DB2 Stored procedure,
In a BPEL service I am getting this error while invoking a DB2 Stored procedure with Strong XSD. I am using assign to copy the input parameter to the input parameters of Stored procedure.
not able to figure out why this error message is coming.
java.lang.Exception: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'JDE_DBA' failed due to: ResultSet XML Conversion Error. An error occurred while converting from a ResultSet to XML. Unable to convert a ResultSet to XML. Cause: java.lang.NullPointerException ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:575) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:381) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:298) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sun.el.parser.AstValue.invoke(AstValue.java:157) at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:283) a
---------------- BPEL Code --------
<?xml version = "1.0" encoding = "UTF-8" ?>

<process name="UPCMatchOrder"
targetNamespace="http://xmlns.oracle.com/CD_JDE_Application_jws/JDE_UPCMatchOrder/UPCMatchOrder"
xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:client="http://xmlns.oracle.com/CD_JDE_Application_jws/JDE_UPCMatchOrder/UPCMatchOrder"
xmlns:ora="http://schemas.oracle.com/xpath/extension"
xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:ns1="http://xmlns.oracle.com/pcbpel/adapter/db/CD_JDE_Application/JDE_UPCMatchOrder/JDE_DBA"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:ns2="http://xmlns.oracle.com/pcbpel/adapter/db/QAMODA73/X56714P/">

<partnerLinks>

<partnerLink name="upcmatchorder_client" partnerLinkType="client:UPCMatchOrder" myRole="UPCMatchOrderProvider"/>
<partnerLink name="JDE_DBA" partnerRole="JDE_DBA_role"
partnerLinkType="ns1:JDE_DBA_plt"/>
</partnerLinks>

<variables>

<variable name="inputVariable" messageType="client:UPCMatchOrderRequestMessage"/>

<variable name="outputVariable" messageType="client:UPCMatchOrderResponseMessage"/>
<variable name="Invoke_1_InputVariable" messageType="ns1:args_in_msg"/>
<variable name="Invoke_1_OutputVariable" messageType="ns1:args_out_msg"/>
</variables>

<sequence name="main">

<receive name="receiveInput" partnerLink="upcmatchorder_client" portType="client:UPCMatchOrder" operation="process" variable="inputVariable" createInstance="yes"/>

<assign name="Assign_3">
<copy>
<from variable="inputVariable" part="InputMessage"/>
<to variable="Invoke_1_InputVariable" part="InputParameters"/>
</copy>
</assign>
<invoke name="Invoke_1" inputVariable="Invoke_1_InputVariable"
outputVariable="Invoke_1_OutputVariable" partnerLink="JDE_DBA"
portType="ns1:JDE_DBA_ptt" operation="JDE_DBA"/>
<assign name="Assign_2">
<copy>
<from variable="Invoke_1_OutputVariable" part="OutputParameters"/>
<to variable="outputVariable" part="OutputMessage"/>
</copy>
</assign>
<reply name="replyOutput" partnerLink="upcmatchorder_client" portType="client:UPCMatchOrder" operation="process" variable="outputVariable"/>
</sequence>
</process>
Regards,
-CD

Hi Sanjay,
The JDBC sender adapter returns the rows selected from the database in the follwoing format.
<resultset>
<row>
<column-name1>column-value</ column-name1>
<column-name2>column-value</ column-name2>
<column-name3>column-value</ column-name3>
</row>
<row>
<column-name1>column-value</ column-name1>
<column-name2>column-value</ column-name2>
<column-name3>column-value</ column-name3>
</row>
</resultset>
This error occurs , when the source datatype you have created for the JDBC adapter does not match with this format. I would suggest that you check the source format along with the occurence of your field.
Regards,
Bhavesh

Regarding conversion of idoc into xml/edifact

hi everyone, i am using 5.0 version and i want to know that without using subsystem can be change my idoc into xml/edifact, if yes then plz let me know procedure
regards,
vimarsh

Hello Vimarsh
Basically you have to following steps in the EDI conversion process:
(1) Send business object (e.g. invoice) as IDoc-XML to external system
(2) EDI converter converts IDoc-XML to EDIFACT (flat file) (e.g. Seeburger, mendelson, etc.)
(3) Send EDI file to EDI provider (e.g. GXS, IBM-IE, Tradanet, etc.)
In our case the EDI conversion takes place on SAP-XI (Note: the EDI converter is not part of SAP-XI but a third-party product). The EDI file is placed on a FTP server and then send via ODEX / OFTP to an EDI provider.
Regards,
Uwe

Conversion of purchasing idoc to xml and sending with FTP to supplier

Hello,
I have a question about something i am not very familar with. And i could not find the answer in this forum.
We have a supplier who wants to receive our orders by EDI.
The plan is to convert the IDOC to XML and to send this XML by FTP to our supplier.
Could anyone give me some hints to achieve this.
usefull help will be rewarded.
Gr., Frank

Hi,
1. Create XML port in WE21.
2. Configer the partner profile in WE20 for required message type.
3. Access the file by using transaction AL11.
Thanks,
Asit Purbey

Conversion of idoc into xml without XI

Hi everyone
i am working on EDI i want to know procedure to convert our idoc into XML without using XI. is it possible, if yes then plz reply me with procedure.
Thanks & Regards
Vimarsh

Hi Nicolai
Thanks for ur suggestion, i have one more doubt regarding this, i got this program to convert my records in XML but whatever output i m getting that comes in form of excell sheet, i am sending you that program which not working,
report zexternalfile .
tables : zzpublisher,
sscrfields.
data: it_publisher like standard table of zzpublisher,
wa_publisher like zzpublisher.
select * from zzpublisher into table it_publisher.
call function 'GUI_DOWNLOAD'
exporting
BIN_FILESIZE =
filename = 'C:\externalfiles\kamal.XLS'
FILETYPE = 'ASC'
APPEND = ' '
write_field_separator = 'X'
HEADER = '00'
TRUNC_TRAILING_BLANKS = ' '
WRITE_LF = 'X'
COL_SELECT = ' '
COL_SELECT_MASK = ' '
DAT_MODE = ' '
IMPORTING
FILELENGTH =
tables
data_tab = it_publisher
EXCEPTIONS
FILE_WRITE_ERROR = 1
NO_BATCH = 2
GUI_REFUSE_FILETRANSFER = 3
INVALID_TYPE = 4
NO_AUTHORITY = 5
UNKNOWN_ERROR = 6
HEADER_NOT_ALLOWED = 7
SEPARATOR_NOT_ALLOWED = 8
FILESIZE_NOT_ALLOWED = 9
HEADER_TOO_LONG = 10
DP_ERROR_CREATE = 11
DP_ERROR_SEND = 12
DP_ERROR_WRITE = 13
UNKNOWN_DP_ERROR = 14
ACCESS_DENIED = 15
DP_OUT_OF_MEMORY = 16
DISK_FULL = 17
DP_TIMEOUT = 18
FILE_NOT_FOUND = 19
DATAPROVIDER_EXCEPTION = 20
CONTROL_FLUSH_ERROR = 21
OTHERS = 22
if sy-subrc 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
IF YOU HAVE ANY OTHER OPTION THEN PLEASE SEND ME, I WILL BE VERY THANKFUL FOR YOU.
PLEASE SEND ME WHOLE PROCEDURE IF YOU CAN.
THANKS & REGARDS
VIMARSH

IDOC-- XML conversion

Hi all,
Could anyone let me know if there is any method of converting IDOC to XML with out using XI or any EAI tools?
Raghav

Raghavan,
If you want to convert an idoc to XML (write to XML file), then ALE has a simple mechanism to do it.
Please read the following post in SDN , wherein we can define a XML port (instead of a file port) to convert a idoc to XML
convert IDOC data to XML format.
Some post also list the required FM to achieve the same

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

How can I convert IDoc in XML format w/DTD into a string?

I want to send by e-mail outbound IDoc in XML format with its document type definition (DTD).
I want to be able to get the same output result into a string than the XML file IDoc port type with DTD activated. I have created a FM (based on SAP "OWN_FUNCTION") assigned to an IDoc port of type ABAP-PI that executes the following processing steps:
1-Extract outbound IDoc information to get the sender & recipient mail addresses (EDP13 / EDIPHONE tables).
2-Convert & Transform IDoc data into XML string using FM IDX_IDOC_TO_XML.
3-Prepare and send e-mail with XML attachement using FM SO_NEW_DOCUMENT_ATT_SEND_API1.
I cand generate the e-mail with the XML file attachement but FM IDX_IDOC_TO_XML does not convert the IDoc with proper formating and DTD.
What should I use to accomplish the IDoc conversion to XML w/DTD into a string?
Should I use XSLT tools ?
How does that work?
Thank you
Carl

muks wrote:
Use decimal string to number
Specifically, you can define a constant with a different datatype on the input on the lower left if you need a different datatype (e.g. U8, I64, DBL, etc) Are all your values integers or do you also need to scan fractional numbers? In this case, you should use "fract/exp string to number" instead.
LabVIEW Champion . Do more with less code and in less time .

Error in Idoc to XML conversion

Similar Messages

Maybe you are looking for