Skip to Content
0

SAP PI - No operation with XML root tag .num exists

Sep 27, 2017 at 10:43 AM

86

avatar image
Former Member

Hi PI Experts,

I have a scenario from file to SFTP,where i have to send the file to receiver side, by prefixing with some "xyz"_filename.for this i wrote one UDF and i am trying to execute the functionaliy,but while i am doing this i am receivning the below error.Could someone light on this?

Below is the error:

Error when determining the receiver: Problem while determining receivers using interface mapping: No operation with XML root tag .num exists. Problem while determining receivers using interface mapping: No operation with XML root tag .num exists. No operation with XML root tag .num exists
my UDF

DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create( "http://sap.com/xi/XI/System/File", "FileName");
String filename = conf.get(key);
String SID = System.getProperty("SAPSYSTEMNAME");
if (SID.equals("PID") || SID.equals( "PIQ") || SID.equals( "PIP"))
{
filename  = "XYZ_" + filename+ "_"  ;
}
conf.put(key,filename);
10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

6 Answers

Evgeniy Kolmakov Sep 27, 2017 at 12:56 PM
0

Hi Amarnath!

Then check the structure and namespaces of your source file against the Message type assigned to your sender interface in ESR.

Regards, Evgeniy.

Share
10 |10000 characters needed characters left characters exceeded
Raghuraman S Sep 27, 2017 at 10:59 AM
0

Are you using FCC here? ensure the namespace is correct

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Sep 27, 2017 at 12:32 PM
0

HI Raghuraman i am not using FCC here..

Share
10 |10000 characters needed characters left characters exceeded
Raghuraman S Sep 27, 2017 at 03:05 PM
0

One more check in the receiver determination uncheck the operation specific button and try.

Show 2 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Hi Raghuraman,

operation specific i tried,the messages are passing through..but i am getting mapping error.I think this is not the correct solution..i mean unchecking of operation specific button.

Thanks,

Amar.

0

After changing what is the mapping error thrown?

0
Mark Dihiansan Sep 28, 2017 at 04:10 AM
0

Hi,

Error when determining the receiver: Problem while determining receivers using interface mapping:

Are you using enhanced receiver determination?

Regards,

Mark

Show 2 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Hi Dihiasnan,

You mean to say.. Extended Receiver determination right? my answer is no.. I am using standard type of Receiver Determination.

Thanks,

Amar

1

Well in that case, check your service interface operation and make sure it matches the one in operation mapping. Aside from that, also check your interface determination configuration.

0
Manoj K Sep 28, 2017 at 07:24 AM
0

Hi,

I believe you have copied the service interface from some existing service interface in this case the operation name remains of old copied service interface only . So create a new outbound service interface with your required message type and also in your interface determination make sure you have "Non-Operation specific". Cross check the incoming xml file with your source structure cross check the namesapce too.

Br,

Manoj

Share
10 |10000 characters needed characters left characters exceeded