cancel
Showing results for 
Search instead for 
Did you mean: 

PO not cretaed On SUS.

Former Member
0 Kudos

Hello Experts,

We are implementing MM-SUS. When PO Idoc gets triggered from MM and Via XI it goes to SUS. In SUS , Tcode, SXMB_MONI, i can see the XML message with Error.

Error message is as follwos:

" Save Stylesheet failed /1SAI/TXSD5BFE2D6C24B57C0071F: Transformation /1SAI/TXSD5BFE2D6C24B57C0071F contains syntax error ".

Please help, because of this error PO not created on SUS.

Please help, We are new to SUS.

Thanks in advance.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

It was XI proxy problem , solved by SAP

Former Member
0 Kudos

Dear Akash,

Please check the following

1.Check idoc status in MM system

2.check in WE 20 tcode the partner profiles "ORDERS" message type exist.

if the idoc at MM system is transfered to SUS and at XI it is failing.

3.check the SLDCHECK tcode.

4.Reprocess the message in STXB_MONI message.

4.Check whether you have maintained SUS po number ranges

Thanks

Raheem

Former Member
0 Kudos

Hi,

Thanks for you reply,

Everything is fine that u mentioned.

It is a error, while sending acknoledgement back to XI from SUS for ORders.

Please let me know how to handle?

Former Member
0 Kudos

Hi Shah

Maintain the inbound parameters in Partner profiles the message type "ALEAUD" and the process code for this AUD1.

generally when you create a purchase order, a acknowledgement response will come back, if you maintain the above message type , will handle this.

Thanks

Raheem

Former Member
0 Kudos

Hi Raheem,

You said, "Maintain the inbound parameters in Partner profiles the message type "ALEAUD" and the process code for this AUD1."

Can you tell me where to maintain this? in R/3 or SUS?

In SUS we do not have any partner profile.

You said " generally when you create a purchase order, a acknowledgement response will come back, if you maintain the above message type , will handle this. " Its right, But let me know the detailed steps how to do it? and where to do it?

Thanks

Aakash

Former Member
0 Kudos

Hi,

Maintain this in partner profile in tcode we 20 in r/3 system.

Thanks

Raheem

Former Member
0 Kudos

Hi,

In r/3 go to tcode we 20, select the partner type LS node on left hand side , select your partner type " like susxxxx", there you can see in the right hand side the outbound parameters and inbound parameters.

at the inbound parameters

maintain the message type as mentioned "ALEAUD"

thanks

Raheem

Award points if useful

Former Member
0 Kudos

Hi Raheem,

I have maintained.But still acknowledgement is stucked and give error.

Please let me know if anything else i have to do?

Thanks.

Former Member
0 Kudos

Hi,

Check with your XI consultant, whether for this message type is mapped into the XI content.

what is the error message you are getting in we05 tcode in r/3.

also send me the sxmb_moni error messge

Thanks

Raheem

Former Member
0 Kudos

Hi Raheem,

In WE05, for mesage type ALEAUD, error is " EDI: Partner Profile inbound not available "

Former Member
0 Kudos

Hi Raheem,

Can you give me your number? if possible? I will call you and will solve the error.

Thanks

aakash.

Former Member
0 Kudos

9703426392

Former Member
0 Kudos

Hi Raheem,

Its not solved yet. Please let me know when can i call you on monday?

Thanks ,

Aaakash

Former Member
0 Kudos

Hi Raheem,

Problem still persists.

Please help.

Former Member
0 Kudos

Hi Akash,

please check your proxy settings on your XI system and SUS system and also check the pakage properly added or not.

Thanks

Raheem

Former Member
0 Kudos

Hi raheem,

Can you tell in detail step, what to check , n how to check?

Former Member
0 Kudos

Hello Raheem,

please check error.

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

- <!-- Call Inbound Proxy

-->

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

<SAP:Category>XIProxy</SAP:Category>

<SAP:Code area="ABAP">SAVE_STYLESHEET_FAILED</SAP:Code>

<SAP:P1>Transformation /1SAI/TXSD5BFE2D6C24B57C0071F contains syntax error</SAP:P1>

<SAP:P2>/1SAI/TXSD5BFE2D6C24B57C0071F</SAP:P2>

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Save Stylesheet failed /1SAI/TXSD5BFE2D6C24B57C0071F: Transformation /1SAI/TXSD5BFE2D6C24B57C0071F contains syntax error</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>