Solved: rfc sender -> text file

I have a interface using rfc sender. When it's executed, a file is created.

When the format is a XML, the file is created, but, when I use "File Content Conversion" in "File Adatper" to convert the data in text format, the file is not created.

The structure of my RFC is:

Y_SD_XI_EDI_NOTFIS  - RFC
  DATA    	    - Table
    TEXT            - Field

The configuration in "File Content Conversion" is:


Recordset Structure:       DATA,* (I already write this using "DATA")
DATA.fileNames:            TEXT
DATA.processConfiguration: fromConfiguration
DATA.endSeparator:         'nl'

What is the problem?

SAP Managed Tags:
SAP HANA,
SAP Process Integration

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (1)

Hi,

If i have understood your target XML correctly you have

DATA as record set structure and Text as the field name.

The configuration should be as given below

Recordset Structure: DATA

DATA.fileNames: TEXT

DATA.endSeparator: 'nl'

What is the error you see in RWB->Message monitoring->Adapterengine

or in RWB->Component monitoring->Adapetr monitoring.

If you have only this structure as you have stated than it should work otherwise there are lot of restriction on using Content conversion as your interface structure should satisfy its predetermined criteria.

Writin your XML will help in providing quick solution.

Hope it helps.

Regards,

Satish

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Satish,

I did the following configuration

Recordset Structure: DATA
DATA.fileNames: TEXT
DATA.endSeparator: 'nl'
DATA.fieldFixedLengths: 500

But, the file wasn't create

The log in RWB is:

Waiting 19.01.2006 15:33:11 19.01.2006 15:33:12   EnviarNotaFiscal   SPASA_EDI urn:spasa_edi.notfis
NotaFiscalInboundAsync 
2006-01-19 15:33:11 Success The message was successfully received by the messaging system. Profile: XI URL: http://sapccnwd:51300/MessagingSystem/receive/AFW/XI 
2006-01-19 15:33:11 Success Using connection AFW. Trying to put the message into the receive queue. 
2006-01-19 15:33:12 Success Message successfully put into the queue. 
2006-01-19 15:33:12 Success The message was successfully retrieved from the receive queue. 
2006-01-19 15:33:12 Success The message status set to DLNG. 
2006-01-19 15:33:12 Success Delivering to channel: FileReceiverNotfis 
2006-01-19 15:33:12 Success File adapter receiver: processing started; QoS required: ExactlyOnce 
2006-01-19 15:33:12 Success File adapter receiver channel FileReceiverNotfis: start processing: party " ", service "SPASA_EDI" 
2006-01-19 15:33:12 Success Connect to FTP server "ftp.discovirtual.terra.com.br", directory "/" 
2006-01-19 15:33:12 Success Write to FTP server "ftp.discovirtual.terra.com.br", directory "/", -> file "notfis20060119-153312-881.txt" 


Successful 19.01.2006 15:33:17 19.01.2006 15:33:17   EnviarNotaFiscal   SPASA_EDI urn:sap-com:document:sap:rfc:functions
Y_SD_XI_EDI_NOTFIS 
2006-01-19 15:33:17 Success Using connection AFW. Trying to put the message into the receive queue. 
2006-01-19 15:33:17 Success The XI response message for message 0349786d-7c8e-844e-a744-29a6a78fa3a4(INBOUND) was successfully returned to the calling application. 
2006-01-19 15:33:17 Success The message status set to DLVD.

And RFC xml is

<?xml version="1.0" encoding="UTF-8" ?> 
- <rfc:Y_SD_XI_EDI_NOTFIS xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
- <E_REG000>
  <IDREG></IDREG> 
  <IDREM></IDREM> 
  <IDDES></IDDES> 
  <DATA></DATA> 
  <HORA></HORA> 
  <IDINT></IDINT> 
  <FILLER></FILLER> 
  </E_REG000>
- <E_REG310>
  <IDREG></IDREG> 
  <IDDOC></IDDOC> 
  <FILLER></FILLER> 
  </E_REG310>
  <SENDER></SENDER> 
- <DATA>
- <item>
  <TEXT>000ALPARGATAS-MOGI 0 1101061442NOT110106785</TEXT> 
  </item>
- <item>
  <TEXT>310NOTFI110114420</TEXT> 
  </item>
- <item>
  <TEXT>31161079117010402456010307119 AV.JOAO PINTO,100 MOGI MIRIM 13803360 SP 11012006SÃO PAUL</TEXT> 
  </item>
- <item>
  <TEXT>312N G VESTUARIO LTDA ME 037901650001009020973096 AV. SAO PAULO,458 - LJ ** AVENIDA CENTERCENTRO MARINGA</TEXT> 
  </item>
- <item>
  <TEXT>313063023223154546PR-INT 120C. 0025755011012006CONFECÇOES CAIXA 0000100000000000008576000009200455NN000000000000000000000000000</TEXT> 
  </item>
- <item>
  <TEXT>313063023223154546PR-INT 120C. 0025755111012006CONFECÇOES CAIXA 0000100000000000012304000011200455NN000000000000000000000000001</TEXT> 
  </item>
- <item>
  <TEXT>312ULYSSES FERREIRA BARBOSA E CIA LTDA 755136140001768220257143 R MIN OLIVEIRA SALAZAR, 4858 ** ** CENTRO UMUARAMA</TEXT> 
  </item>
- <item>  <TEXT>318000000000295472000000000004013000000000003798000000000001900000000000014037000000000000000</TEXT> 
  </item>
  </DATA>
  <T_REG311></T_REG311> 
  <T_REG312></T_REG312> 
  <T_REG313></T_REG313> 
  <T_REG314></T_REG314> 
  <T_REG315></T_REG315> 
  <T_REG316></T_REG316> 
  <T_REG317></T_REG317> 
  <T_REG318></T_REG318> 
  </rfc:Y_SD_XI_EDI_NOTFIS>

Hi,

I dont see any error in MDT as you have sent and it seems message has been delivered. The final ststus is DVLD.

So there is no error by File adapter. File(notfis20060119-153312-881.txt) has to be there at the desired location. have you given the root directory for target file?

1. Try writing file other than root Directory. Just a suggestion. There should not be a problem though?????

2. If you dont use content conversion than it writes XML file correctly rt. Can you pass that XML.

The XML you have sent me is Sender side i.e RFC XML, i am more interested in target side as that XML is going to be converted by content conversion.

Regards,

Satish

I'm creating the File in root, because this is a test yet. After, I will put in correct directory.

When I don't use the "content conversion" the file is created.

The file XML created is:

Thank you for your help

Hi,

Did you check in Adapter monitoring this kind of errors you get there. The status goes red with specific error.

I think i have got the problem. since there are multiple recordset structure you cannot give just one recordset. If you give just one recordset it applies to all other in the structure. If the structure is diffrent for recordset structure than you have to pass all recordset structure.

You can cut the recordset if you dont want it in output file. for e.g to cut E_REG000

E_REG000.fixedLengthTooShortHandling: CUT

The configuration should be: all the recordset

Recordset Structure: E_REG000,E_REG310,item

DATA.fileNames: TEXT

DATA.endSeparator: 'nl'

DATA.fieldFixedLengths: 500

E_REG000.fieldFixedLengths: 0

E_REG000.fixedLengthTooShortHandling: CUT

and so on........

Noe here is the tricky part

<T_REG311 />

<T_REG312 />

<T_REG313 />

<T_REG314 />

<T_REG315 />

<T_REG316 />

<T_REG317 />

<T_REG318 />

are not recordset structure as there are no fields under it. So you cannot process this structure through content conversion. This is the limitation your structure should follow some protocols.

Solution can be. If you want only TEXT in output file just have that structure in target message and do your mapping from RFC str to target structure and write this through content conversion.

Hope i have not confused you.

Regards,

satish

Hi,

I changed the RFC. Now, there is only DATA table and a Import Parameter.

I'm still with same problem.

I see that when I run the process don't using the Content Conversion, all the logs in RWB is "Successful", but, when I run using "Content Conversion", one log was "Waiting" (aways were generated three logs).

The log detail for process using "Content Conversion" is equal to process that dont use "Content Conversion".

The detail is:

code]2006-01-19 19:31:08 Success The message was successfully received by the messaging system. Profile: XI URL: http://sapccnwd:51300/MessagingSystem/receive/AFW/XI

2006-01-19 19:31:08 Success Using connection AFW. Trying to put the message into the receive queue.

2006-01-19 19:31:08 Success Message successfully put into the queue.

2006-01-19 19:31:08 Success The message was successfully retrieved from the receive queue.

2006-01-19 19:31:08 Success The message status set to DLNG.

2006-01-19 19:31:08 Success Delivering to channel: FileReceiverNotfis

2006-01-19 19:31:08 Success File adapter receiver: processing started; QoS required: ExactlyOnce

2006-01-19 19:31:08 Success File adapter receiver channel FileReceiverNotfis: start processing: party " ", service "SPASA_EDI"

2006-01-19 19:31:08 Success Connect to FTP server "ftp.discovirtual.terra.com.br", directory "/"

2006-01-19 19:31:08 Success Write to FTP server "ftp.discovirtual.terra.com.br", directory "/", -> file "notfis20060119-193108-773.txt"[/code]

See all my configuration, design, XML's and others:

+++ Design +++

Message Interfaces
[NotaFiscalAbstractAsync]
[NotaFiscalAbstractSync]

Integration Process
[NotaFiscalIP]

- Receiver1 -> Sender1 -> Sender2

- Container
  Name     		Type
  AbstractMessage	NotaFiscalAbstractAsync

- Receiver1 			
  Mode:			  Open S/A bridge
  Synchronous Interface:  NotaFiscalAbstractSync 
  Message:		  AbstractMessage

- Sender1
  Mode:			  Asynchronous
  Message: 		  NotaFiscalAbstractAsync

- Sender2
  Mode:			  Close S/A bridge
  Message: 		  NotaFiscalAbstractSync

+++ Configuration +++

Business Service: SPASA_EDI

Receiver Determination
- SPASA_EDI | Y_SD_XI_EDI_NOTFIS
  Service: NotaFiscalIP - Receiver:  NotaFiscalAbstractAsync

- NotaFiscalIP | NotaFiscalAbstractAsync
  Service: SPASA_EDI - Receiver:  NotaFiscalAbstractAsync
 
Sender Agreement
-SPASA_EDI | Y_SD_XI_EDI_NOTFIS


+++ RFC +++
Import
  Sender
Tables
  DATA ( TEXT CHAR(300) )
  
+++ XML Sender +++

 <?xml version="1.0" encoding="UTF-8" ?> 
- <rfc:Y_SD_XI_EDI_NOTFIS xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
  <SENDER></SENDER> 
- <DATA>
- <item>
  <TEXT>000ALPARGATAS-MOGI 0 1101061442NOT110106785</TEXT> 
  </item>
- <item>
  <TEXT>310NOTFI110114420</TEXT> 
  </item>
- <item>
  <TEXT>31161079117010402456010307119 AV.JOAO PINTO,100 MOGI MIRIM 13803360 SP 11012006SÃO PAUL</TEXT> 
  </item>
- <item>
  <TEXT>312N G VESTUARIO LTDA ME 037901650001009020973096 AV. SAO PAULO,458 - LJ ** AVENIDA CENTERCENTRO MARINGA</TEXT> 
  </item>
- <item>
  <TEXT>313063023223154546PR-INT 120C. 0025755011012006CONFECÇOES CAIXA 0000100000000000008576000009200455NN000000000000000000000000000</TEXT> 
  </item>
- <item>
  <TEXT>313063023223154546PR-INT 120C. 0025755111012006CONFECÇOES CAIXA 0000100000000000012304000011200455NN000000000000000000000000001</TEXT> 
  </item>
- <item>
  <TEXT>312ULYSSES FERREIRA BARBOSA E CIA LTDA 755136140001768220257143 R MIN OLIVEIRA SALAZAR, 4858 ** ** CENTRO UMUARAMA</TEXT> 
  </item>
- <item>
  <TEXT>313063023223154547PR-INT 120C. 0025755211012006CONFECÇOES CAIXA 0000100000000000018192000014500300NN000000000000000000000000000</TEXT> 
  </item>
- <item>
  <TEXT>313063023223154547PR-INT 120C. 0025755311012006CONFECÇOES CAIXA 0000100000000000024487000016500300NN000000000000000000000000001</TEXT> 
  </item>
- <item>
  <TEXT>312MOURIZE ZANANDRA SCHIMDT DE S.FREIRE ELL055724850001019027647046 RUA HAROLDO HAMILTON, 478 - SALA 6 ** **CENTRO TOLEDO</TEXT> 
  </item>
- <item>
  <TEXT>313063023223154548PR-INT 120C. 0025755411012006CONFECÇOES CAIXA 0000100000000000028314000019800242NN000000000000000000000000001</TEXT> 
  </item>
- <item>
  <TEXT>312L GASPAR PROENCA E MG PROENCA LTDA 01109275000120251311376 AV. PARANA, 224 ** ** CENTRO IVAIPORA</TEXT> 
  </item>
- <item>
  <TEXT>313063023223154549PR-INT 120C. 0025755511012006CONFECÇOES CAIXA 0000100000000000009780000009200437NN000000000000000000000000000</TEXT> 
  </item>
- <item>
  <TEXT>313063023223154549PR-INT 120C. 0025755611012006CONFECÇOES CAIXA 0000100000000000016673000012000437NN000000000000000000000000001</TEXT> 
  </item>
- <item>
  <TEXT>312LZK MATERIAIS ESPORTIVOS LTDA - ME 07639256000192255067003 RUA 23 DE JULHO, 291 - SALA 2 ** ** CENTRO POUSO RED</TEXT> 
  </item>
- <item>
  <TEXT>313063023223154550SC-INT 120C. 0025755711012006CONFECÇOES CAIXA 0000100000000000013140000011800306NN000000000000000000000000000</TEXT> 
  </item>
- <item>
  <TEXT>313063023223154550SC-INT 120C. 0025755811012006CONFECÇOES CAIXA 0000100000000000026964000018500306NN000000000000000000000000001</TEXT> 
  </item>
- <item>
  <TEXT>312FUTEBOL MANIA COM LTDA 00845448000106253191831 RUA TENENTE SILVEIRA 141 ** ** CENTRO FLORIANOP</TEXT> 
  </item>
- <item>
  <TEXT>313063023223154575SC-CAP 120C. 0025754811012006CONFECÇOES CAIXA 0000700000000000106188000180600312NN000000000000000000000000002</TEXT> 
  </item>
- <item>
  <TEXT>312ULISSES ALCANTARA 814284010001493010273110 R CARLOS CAVALCANTI 99 ** CENTRO UNIAO DA</TEXT> 
  </item>
- <item>
  <TEXT>313063023223154576PR-INT 120C. 0025754911012006CONFECÇOES CAIXA 0000300000000000030854000097800248NN000000000000000000000000001</TEXT> 
  </item>
- <item>
  <TEXT>318000000000295472000000000004013000000000003798000000000001900000000000014037000000000000000</TEXT> 
  </item>
  </DATA>
  </rfc:Y_SD_XI_EDI_NOTFIS>

+++ XML File/Response (didn't using "Content Conversion") +++


<?xml version="1.0" encoding="UTF-8"?><rfc:Y_SD_XI_EDI_NOTFIS xmlns:rfc="urn:sap-com:document:sap:rfc:functions"><SENDER></SENDER><DATA><item><TEXT>000ALPARGATAS-MOGI                    0                                  1101061442NOT110106785</TEXT></item><item><TEXT>310NOTFI110114420</TEXT></item><item><TEXT>31161079117010402456010307119   AV.JOAO PINTO,100                       MOGI MIRIM                         13803360 SP       11012006SÃO PAUL</TEXT></item><item><TEXT>312N G VESTUARIO LTDA ME                   037901650001009020973096     AV. SAO PAULO,458 - LJ ** AVENIDA CENTERCENTRO              MARINGA</TEXT></item><item><TEXT>313063023223154546PR-INT 120C.  0025755011012006CONFECÇOES     CAIXA          0000100000000000008576000009200455NN000000000000000000000000000</TEXT></item><item><TEXT>313063023223154546PR-INT 120C.  0025755111012006CONFECÇOES     CAIXA          0000100000000000012304000011200455NN000000000000000000000000001</TEXT></item><item><TEXT>312ULYSSES FERREIRA BARBOSA E CIA LTDA     755136140001768220257143     R MIN OLIVEIRA SALAZAR, 4858 ** **      CENTRO              UMUARAMA</TEXT></item><item><TEXT>313063023223154547PR-INT 120C.  0025755211012006CONFECÇOES     CAIXA          0000100000000000018192000014500300NN000000000000000000000000000</TEXT></item><item><TEXT>313063023223154547PR-INT 120C.  0025755311012006CONFECÇOES     CAIXA          0000100000000000024487000016500300NN000000000000000000000000001</TEXT></item><item><TEXT>312MOURIZE ZANANDRA SCHIMDT DE S.FREIRE ELL055724850001019027647046     RUA HAROLDO HAMILTON, 478 - SALA 6 ** **CENTRO              TOLEDO</TEXT></item><item><TEXT>313063023223154548PR-INT 120C.  0025755411012006CONFECÇOES     CAIXA          0000100000000000028314000019800242NN000000000000000000000000001</TEXT></item><item><TEXT>312L GASPAR PROENCA E MG PROENCA LTDA      01109275000120251311376      AV. PARANA, 224 ** **                   CENTRO              IVAIPORA</TEXT></item><item><TEXT>313063023223154549PR-INT 120C.  0025755511012006CONFECÇOES     CAIXA          0000100000000000009780000009200437NN000000000000000000000000000</TEXT></item><item><TEXT>313063023223154549PR-INT 120C.  0025755611012006CONFECÇOES     CAIXA          0000100000000000016673000012000437NN000000000000000000000000001</TEXT></item><item><TEXT>312LZK MATERIAIS ESPORTIVOS LTDA - ME      07639256000192255067003      RUA 23 DE JULHO, 291 - SALA 2 ** **     CENTRO              POUSO RED</TEXT></item><item><TEXT>313063023223154550SC-INT 120C.  0025755711012006CONFECÇOES     CAIXA          0000100000000000013140000011800306NN000000000000000000000000000</TEXT></item><item><TEXT>313063023223154550SC-INT 120C.  0025755811012006CONFECÇOES     CAIXA          0000100000000000026964000018500306NN000000000000000000000000001</TEXT></item><item><TEXT>312FUTEBOL MANIA COM LTDA                  00845448000106253191831      RUA TENENTE SILVEIRA  141 ** **         CENTRO              FLORIANOP</TEXT></item><item><TEXT>313063023223154575SC-CAP 120C.  0025754811012006CONFECÇOES     CAIXA          0000700000000000106188000180600312NN000000000000000000000000002</TEXT></item><item><TEXT>312ULISSES ALCANTARA                       814284010001493010273110     R CARLOS CAVALCANTI 99 **               CENTRO              UNIAO DA</TEXT></item><item><TEXT>313063023223154576PR-INT 120C.  0025754911012006CONFECÇOES     CAIXA          0000300000000000030854000097800248NN000000000000000000000000001</TEXT></item><item><TEXT>318000000000295472000000000004013000000000003798000000000001900000000000014037000000000000000</TEXT></item></DATA></rfc:Y_SD_XI_EDI_NOTFIS>

+++ Log Using Content Conversion

  Successful 19.01.2006 19:33:36 19.01.2006 19:33:36   EnviarNotaFiscal   SPASA_EDI urn:sap-com:document:sap:rfc:functions
Y_SD_XI_EDI_NOTFIS 
   Successful 19.01.2006 19:33:27 19.01.2006 19:33:27   EnviarNotaFiscal   SPASA_EDI urn:spasa_edi.notfis
NotaFiscalAbstractAsync 
   Successful 19.01.2006 19:33:18 19.01.2006 19:33:36   SPASA_EDI     urn:sap-com:document:sap:rfc:functions
Y_SD_XI_EDI_NOTFIS

+++ Log when I didn't Use "Content Conversion"

   Successful 19.01.2006 19:31:16 19.01.2006 19:31:16   EnviarNotaFiscal   SPASA_EDI urn:sap-com:document:sap:rfc:functions
Y_SD_XI_EDI_NOTFIS 
   <b>Waiting</b> 19.01.2006 19:31:08 19.01.2006 19:31:08   EnviarNotaFiscal   SPASA_EDI urn:spasa_edi.notfis
NotaFiscalAbstractAsync 
   Successful 19.01.2006 19:31:06 19.01.2006 19:31:16   SPASA_EDI     urn:sap-com:document:sap:rfc:functions
Y_SD_XI_EDI_NOTFIS

Hi,

Did you see the file adapter status in adapter monitoring (RWB->Component monitoring->Adapter engine->Adapter monitoring -> File adapter->youe communication channel name.

It should show you red status when you use content conversion with the error history. (Message is shown successful in MDT but fails while writing to the target directory).

Since message is in waiting just check the details (audit log).

Your scenario is RFC->XI->FILE. In BPM you have used sync aysnc bridge, what exactly you are planning to do.

Regards,

Satish

I was using "Integration Process" to transfer syncrhonous to assyncronous messages, but I don't now if this is needed.

Now, I removed the Integration Process.

The folowing error ("DUMP") is generated in ABAP program, but the xml file is created. There are not logs im SXMB_MONI.

"failed to identify XML document:org.xml.sax.SAXParseException: Document root"

When I use "Content Conversion", is showed this error in ABAP Program: call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException:

In SXMB_moni, the error is:

com.sap.aii.af.ra.ms.api.DeliveryException: java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Consistency error: more fields found in XML structure than specified in conversion parameters! (Value '310NOTFI110114420')', probably configuration error in file adapter (XML parser error)'

This is the limitation of reciver adapter that if the output structure going for content conversion is not in formt of

Recordset

Field

You cannot conver it.

In your case the structure is

Sender(Recordset1 structure, but there is no child to it)

and

Data

Item (recordset 2 it has a child Text which you want to output in file)

Text

Can you try one thing in mapping program just disable the sender node and map Item and text the way you are doing.

Than use content conversion and pass

Item in recordset structure, not DATA.

rest all parameters are same as you have already given , than it will convert.

What happens is you give recorset structure as data or item and in XML message adapter finds a node SENDER so it throws an error saying what to do with this. since it is not recordset(because there is no child element under it).

Either your structure should be recorset str->field or disable the sender in mapping program so that it is not there in target XML. If you want your sender field data in target that you have to make a structure like mentioned abaove.

Hope it helps,

Regards,

Satish

I did some changes. Now, the text file was create with one line only.

I created a data type and a message type:

NotaFiscal 1..1

record 1..1

row 0..ubounded

text 1..1

I created the folowing Messages Interfaces:

NotaFiscalInboundAsync : NotaFiscal

I did a Message Mapping

Y_SD_XI_EDI_NOTFIS - NotaFiscal

DATA - Row

item

TEXT - text

My configuration is:

Sender: Y_SD_XI_EDI_NOTFIS

Receiver Determination:

- Sender Y_SD_XI_EDI_NOTFIS

- receiver NotaFiscalInboundAsync

- Mapping Y_SD_XI_EDI_NOTFIS -> NotaFiscalInboundAsync.

Error (with dump in ABAP):

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Request Message Mapping

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code>

<SAP:P1>urn:spasa_edi.notfis NotaFiscalOutboundAsync_NotaFiscalInboundAsync_IM</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Unable to determine name of mapping program</SAP:Stack>

<SAP:Retry>N</SAP:Retry>

</SAP:Error>

Now, the target is:

recordset structure: row

row.endSeparator = 'nl'

row.fieldFixedLengths = 300.

I did some changes. Now, the text file was create with one line only.

I created a data type and a message type:

NotaFiscal 1..1

record 1..1

row 0..ubounded

text 1..1

I created the folowing Messages Interfaces:

NotaFiscalInboundAsync : NotaFiscal

I did a Message Mapping

Y_SD_XI_EDI_NOTFIS - NotaFiscal

DATA - Row

item

TEXT - text

My configuration is:

Sender: Y_SD_XI_EDI_NOTFIS

Receiver Determination:

- Sender Y_SD_XI_EDI_NOTFIS

- receiver NotaFiscalInboundAsync

- Mapping Y_SD_XI_EDI_NOTFIS -> NotaFiscalInboundAsync.

Error (with dump in ABAP):

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Request Message Mapping

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code>

<SAP:P1>urn:spasa_edi.notfis NotaFiscalOutboundAsync_NotaFiscalInboundAsync_IM</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Unable to determine name of mapping program</SAP:Stack>

<SAP:Retry>N</SAP:Retry>

</SAP:Error>

Now, the target is:

recordset structure: row

row.endSeparator = 'nl'

row.fieldFixedLengths = 300.

You are missing some steps in configuration.

Did you pass Interface mapping in Interface determination.

At runtime it is not getting the mapping program.

Also check you XML payload is mapped correctly by downloading the source xml from SXMB_MONI and testing it in Integration Repository by mapping program.

Regards,

satish

Satish,

I generated a XML file in this format:

after, I create a file sender to get this file (to test) for to create a file text.

My configurations are:

recordset: row

row.endSeparator 'nl'

row.fieldFixedLengths 300.

But the file is not created. In RWB, the status is waiting...

Hi,

The file should be written to the target directory, any ways,

What is the audilt log message of waiting step in RWB i.e MDT, it is displaying it is waiting because of.....

Did you see what happens to the status of File CC in adapter monitoring in RWB when it is in waiting step.

some suggestions.

1. try changing root directory to some other like /test etc...(test directory should have necessary rights)

2. instead of fixed length try giving comma (,) row.fieldSeparator = , Although there is one field item under row ...so it is just a try....

I assume when you dont use content conversion your output file is the XML you have generated in above thread.

Regards,

Satish

My problem is solved

I has a following xml:

And I did this configurations for Content Conversion:

row.fieldSeparator 'nl'

row.endSeparator 'nl'

row.processConfiguration fromConfiguration

row.fieldnames item

Thanks for all answers!

Good to know it worked

Regards,

satish

Answers (1)

HI,

If the file is not getting created means the file content conversion is not working.

Trouble shooting steps.

1. Just check whether the file is being picked up or not from source directory?

2. if the file is not picked up,check up the file properties and folder properties.all should be rwx-rwx-rwx.

3. iof the file is picked up and not getting created,

check the target directory, even is should have rwx properties.

4. even if all are there and still file is not created,

then check the content conversion parameters,there should be error in that only.

Hope this should solve your problem

Regards

Chandra Shekar

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Ask a Question

Top Q&A Solution Author

User

Count

rfc sender -> text file

Accepted Solutions (1)

Accepted Solutions (1)

Answers (1)

Answers (1)

Re: Sending email from UI5 application

Re: Feature Request: Allow Process Intelligence Co...

Store attachments from Standard Fiori apps in Arch...

TR is imported into production but status in Solma...

Re: How to configure SAP system in Eclipse ?