MM SUS issues

[kaus_desh]

Hello All

We are having challenging issues in MM SUS with classic scenario

1) We have a PO changed in ECC - PO with service line item and qty at schedule line is 100 EA and 1 USD and at Item header or main line Price is 100 USD and Qty is 1EA , beacuse of this qty and price at item and schedule line vendor is not able to making the correct Confirmation in SUS portal.

His qty is never matching. and if he tries to match qty then price is going exceptionally high.

Can we solve this issue by changeing ECC PO for schedule line qty and price only ??

2) We are getting service lines in PO and vendor is genrating the SERVICE ENTRY SHEET via confirmation but his confirmation are going in status as " Rejected by customer".

We have observed XML is failed in ECC with error as

<SAP:Stack>Application has thrown an exception

is there any program or FM to change the status of confirmation in SUS ?? there is no note found on this issue , we have reffered below KBA but that is also not useful

Note 1971662:Creation of service entry sheet fails in ECC, open quantity mismatch between SUS and ECC

Kaustubh

[Former Member]

Hi,

question one I didn't fully understand. Also it would be good to know which versions you're on.

How does the service entry sheet look for the vendor after pressing the create button?

He should see something like:

Line 1: Hierarchy

1.1 Service 1

1.2 Service 2

.

.

.

Which price is shown for the service lines?

As for question 2:

If the service entry sheet creation fails inbound ECC, the return XML automatically updates the status of the SUS service entry sheet to REJECTED.

You can mess around with updating the Status in SUS using custom report but I would strongly advise against ist.

If the service entry sheet creation fails, the usual way of handling it is:

1.     Find out why the creation fails . For this you need to debug the inbound XML --> Ask your developer how to do it. Usually you'll get a detailed error message while debugging from one of the function modules/methods that are used.

2.     If you found the error, than correct it. Sometimes master data is wrong, sometimes you have to additionally map data in the inbound data, sometimes an OSS note needs to be implemented and sometimes the vendor needs to change something in the SUS service entry sheet. Could be anything.

3.     After the error was corrected the vendor needs to copy the rejected service entry sheet and send it again. If the error came because of some missing data in SUS, the vendor needs to add this data to the copied service entry sheet.

This is the correct way of doing, everything else is messing with the SUS status management.

Markjs