on 02-09-2012 3:29 PM
Dear all,
I need to
1) send IDOCs (from SAP system) to a FTP server as IDOC Flat File (works)
2) pick up flatfile IDOCs from FTP and send them to SAP system (does not work)
Scenario 1 works and the module IDOCXmlToFlatConvertor converts the IDOC successfully to flat format.
The 2. scenario will not work.
I used [this blog|http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/13743] for creating the scenario.
My error in CC: Error: java.lang.NumberFormatException: For input string: ""
Found [this solution|http://wiki.sdn.sap.com/wiki/display/stage/IDOCFlatToXmlConvertor] for this error, but could not understand the solution given.
In the comments of the blog is this solution :
We have over come the number format exception by placing unique identifier in place of Idoc number and segment relations ships. [...] The limitation is in the format of the source file. The flat file should contain unique identifier in place of IDoc and Parent and child node relation ship should explicitly mentioned in the IDoc flat file.
In my example, no IDOC number is maintained. If I insert a randomized number in header line, I got following error:
MP: exception caught with message Invalid DOCNUM detected. SEGDOCNUM = DOCNUM = 0000000001163320
- Do I need to add this IDOC number to every segment?
- Does the module compare the IDOC number with the system?
- How can I debug a module more in detail. Can I raised the debug level?
- PI System is 7.11. SAP system is 7.01. The flatfile IDOCs have as SAP release level 4.6C (seems to be
the SAP system where the flat files have been genereated from).
As module parameter SAPRelease I inserted 7.01 because he should validate the IDOC against our SAP system.
IDOC- and MES-Type are the same on both systems.
Is this ok?
- Where to find definitions for the structure? As far as I know, the IDOC num needs to be added to
every line. I need to know at which position.
- Does anyone have an example message that could be read in?
Thanks
Chris
Edited by: Christian Riekenberg on Feb 10, 2012 10:46 AM - Added a question
Edited by: Christian Riekenberg on Feb 10, 2012 10:47 AM
I know this is an old post, but I'm experiencing the exact same issue. Do you recall you managed to solve this issue?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
>>>- Does anyone have an example message that could be read in?
it seems you only need one thing in all this long post real IDOC...
create one in WE19 (using your idoc type) and send it to a file port (flat file) - WE19 (without the use of a PI even)
then take this idoc and compare with what you receive in the ftp
is that possible at your end ?
Regards,
Michal Krawczyk
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I just figure out, that there need to be an administrative section in the flat file,
like described in [this document|http://www.scribd.com/doc/56128319/53/Comparing-Flat-File-Structure-to-IDoc-Structure].
How to know, which length this section need to have for each flat file IDOC?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.