on 04-28-2010 5:58 AM
Hello,
I am trying to create a message from the SOLAR01 t-code. System creates the message and displays the following:
Green Tick mark- Message <nn> created successfully in the system <SID>. Basis message not created.
It does not give any error here.
1. However, I cannot see the message under the Messages tab and also when I add it, the system tells me "Message <nn> does not exist".
The message exists when viewed using the transaction monitor.
The system is on EPH1 and using YLFN for the service desk message.
2. Should I define a new entry for YLFN in the basis message settings or use SLF1 only?
Please help.
Thanks,
Rinkal
Hello Rinkal,
When you create a message from SOLAR01, the information that appears in the messages tab comes exclusively from the SLF1.
There is an issue with the creation of SLF1 basis messages. Please check the actions tab of the message in CRMD_ORDER, there might be some warning in the actions tab about the action to create the SLF1. You could also check if you have any issues in SLF1 creation from NOTIF_CREATE, or from help -> create support message.
Unless you solve this issue with the SLF1, there will not be any information in the SOLAR01.
Sorry that I cannot give you more tips about troubleshooting the SLF1 creation, if there are no error messages I don't know where to start looking.
Best regards,
Miguel Ariñ
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
If you open an YLFN, and click on the document flow button, you should see a link to a previous document, that is the SLF1 ABA notification.
Please also check DNO_CUST01, there should be the settings for SLF1.
SLF1 is created from an action when the Service Desk message is created from NOTIF_CREATE or from CRMD_ORDER.
When creating from help -> create support message, the SLF1 is created first, and the CRM part of the Service Desk message is created from an action in the SLF1's action profile. So it is worth to test all ways of creating messages and troubleshooting the errors that may appear.
Best regards,
Miguel Ariñ
Hello Rinkal,
The status profile in DNO_CUST01 is empty in the standard.
Have you checked if your YLFN has an SLF1 in the document flow? If it does not, there will be issues to send the message to SAP.
In case that the YLFN does indeed have an associated SLF1:
Could you please check the number range for SLF1? I have observed similar problems in an issue where the SLF1 was using numbers that had already been assigned in the past. The 'current number' of the interval 1 of number range object DNO_NOTIF had been reset and it was using already used numbers. That made the SOLAR01 throw the error "Message does not exist".
Best regards,
Miguel Ariñ
Hi,
The number ranges are as follows;
Object CRM_SERVICE:
ID From to Current
01 0000000001 0000010000 0
02 0000010001 0000020000 External
Object: DNO_NOTIF:
000000010001 to 0000020000 0
Also, there is no value in the document flow. As I said, the document flow button is disabled.
Now, when I create a message from Help- Create Support message, the message gets created successfully as seen in the transaction monitor, but still gives the error 513. I have checked notes 824640 & 864195. Unable to see where now the issue is.
Please help.
Thanks,
Rinkal
Edited by: Rinkal Salia on Apr 28, 2010 3:50 PM
Hello Rinkal,
When you create a message from help -> create support message, the SLF1 is created first, and after the CRM part is created through an action in the SLF1 action profile. Have you checked that in this case the SLF1 is present?
When you create a message from NOTIF_CREATE or from SOLAR01 (they use mostly the same code), first the CRM part is created, then the ABA notification (SLF1) is created through an action. In the case of action profile AI_SDK_STANDARD, action
AI_SDK_STANDARD_UPDATE_DNO is responsible for this. Do you have an equivalent action in your YLFNs action profile?
Best regards,
Miguel Ariñ
User | Count |
---|---|
98 | |
11 | |
11 | |
10 | |
10 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.