Mail after IDOC Processing...
HI,
After processing an IDOC, whether it is successful or failure I need to send a mail to the respective user about that IDOC status. How we can achieve this please help me.
Thx
Hi Pandu,
You can have workflow in place for Idoc Error handling wherein it will send email to respective user.
you can refer links:
Send alert to business users when IDOC receiver processing fails in SAP ERP
http://www.erpgenie.com/sap-technical/workflow/display-workflow-log-for-an-idoc
http://www.scribd.com/doc/7179710/Error-Handling-on-Inbound-Idocs
Other option is you can go for BPM in PI side.
Regards,
Vivek
Similar Messages
-
Have to send mail if IDOC processing Fails
Hi all,
I am facing a problem here .. i have an idoc which updates 4 ' Z ' tables ..if by chance any 1 of the 4 tables are not updated. exception occurs ... now i have to send a mail regarding the IDOC which failed to updated to an authorized person..
my Question is ... Can we do this using any Function Module or we have to handle this senario using Workflow... as far as i have an idea i can use workflow.. but before that i would like to know if there is any FM that can serve my purpose.
please Suggest...
Usefull Answers will surely be rewarded.
Thanks in ADvance
regards
SrinivasHi ,
For updating yourfour Z tables you probably use custom function module from the process code?
If yes why don't you use SO_OBJECT_SEND.
I think you don't need a workflow for this.
aRs -
Strange result of IDoc processing in the LSMW
Hi
I am using MATMAS_MASS_BAPI IDoc in the LSMW to transfer material master data into client's SAP system. After IDoc processing I got green message with text that application document was successfully processed (IDoc
status = 53). But I can't view created materials using MM03 transaction. Then, records number in the MARA table before and after launching of LSMW is equal. What may be a reason of this situation? How to solve this problem?
Edited by: Marat on Nov 4, 2008 5:24 PMHi there
take a look at the Idoc overview, there should be a t100 message in there if there is a data issue with the idoc BAPI load. However this could be something inconclusive such as 'Inconsistent characteristics' or suchlike. In which case you'll have to check the data and that it matches the requirement for the object -
In 'mail', after importing mailboxes the process gets stuck on '1619 of 72826' and 'time remaining' climbs infinitely. Please suggest a solution.
I converted my mail boxes from POP to imap for the purpose of syncing all my devices. I backed up my mail boxes and further more perfomed a timemachine backup.
Upon restoring ther mailboxes, either by manually copying them to the mailboxes folder, and restoring a timemachine backup, both pocesses result in the above problem.
Please recomend a solution.
file://localhost/Users/redwood/Desktop/Screen%20Shot%202013-10-15%20at%201.48.10 %20PM.png
file://localhost/Users/redwood/Desktop/Screen%20Shot%202013-10-15%20at%201.38.30 %20PM.pngCan anyone out there please help!
-
Send mail to a specific user group when an Inbound Idoc processing fails
I am using standard Message type DEBMAS, but the process code is customed (say ZDEBM as the function module is customed). Can you tell me what configurations are required to activate the error notification message to a user when the inbound idoc fails?
hi,
i think u need to check tcode swu3 for automatic workflow customizing and check in we40 (error AND STATUS PROCESSING) whether the processing code is assigned to the workflow task.
if it is assigned,the workflow will be automatically triggered and the mail will be sent to the user by itself.
ALE error handling uses workflow. A standard task is provided for each message type. Task TS20000051 is used for all BAPIs.
Workflow functions as follows:
A task (work item) is generated for the error handling and stored as a message in the inboxes of the employees responsible.
If one of these employees processes the work item, the standard task method for error handling is started. The user can, for example, restart IDoc processing.
If the IDoc is processed successfully, the work item is deleted from the inboxes of all the employees involved.
For this procedure to function, the employees responsible for a particular message type and partner (sender or receiver) must be defined as follows:
1. A hierarchy of organizational units (for example, "sales office") and positions (for example, "customer officer for customer X") is created and employees are assigned to it.
2. The standard tasks for error handling (for example, an error related to an inbound sales order) are assigned to the relevant organizational units or positions (for example, "sales office").
3. The organizational unit, position or employee responsible for dealing with the error are specified for each partner and message type in the partner profiles.
If an error occurs, the system determines:
1. The employees responsible using the staffing schedule of the organizational unit or position linked to the standard task.
2. The employees defined in the partner profiles (using position, user ID, or organizational unit).
3. The employees appearing in both groups represent those who will receive a work item in their inboxes.
regards,
pankaj singh -
Cannot open mail after upgrade to Yosimite 10.10.1
Hello everyone,
I cannot open mail after I just update from OS X v10.9 (Mavericks) to Yosimite 10.10.1 and I use console to capture the log as below. Pls. help to find the solution.
Thank you
Spaide
1/2/2558 BE 7:14:13.222 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
1/2/2558 BE 7:14:14.605 PM bird[859]: Assertion failed: ![_xpcClients containsObject:client]
1/2/2558 BE 7:14:14.606 PM bird[859]: Assertion failed: ![_xpcClients containsObject:client]
1/2/2558 BE 7:14:14.935 PM bird[859]: Assertion failed: ![_xpcClients containsObject:client]
1/2/2558 BE 7:14:26.958 PM Mail[941]: *** Assertion failure in -[MFIMAPAccount mailboxForRelativePath:isFilesystemPath:create:], /SourceCache/Mail/Mail-1993/MailFramework/Accounts/MFMailAccount.m:4467
1/2/2558 BE 7:14:27.595 PM Mail[941]: An uncaught exception was raised
1/2/2558 BE 7:14:27.596 PM Mail[941]: Absolute path passed into -[MFIMAPAccount mailboxForRelativePath:isFilesystemPath:create:]: /็Homeworks
1/2/2558 BE 7:14:27.596 PM Mail[941]: (
0 CoreFoundation 0x0000000111c5764c __exceptionPreprocess + 172
1 libobjc.A.dylib 0x000000010ffe26de objc_exception_throw + 43
2 CoreFoundation 0x0000000111c5742a +[NSException raise:format:arguments:] + 106
3 Foundation 0x000000010fb435b9 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 195
4 Mail 0x000000010f402f5c -[MFMailAccount mailboxForRelativePath:isFilesystemPath:create:] + 251
5 Mail 0x000000010f360404 -[MFIMAPAccount mailboxForRelativePath:isFilesystemPath:create:] + 491
6 Mail 0x000000010f404696 +[MFMailAccount mailboxForURL:forceCreation:syncableURL:] + 473
7 Mail 0x000000010f41b168 __43+[MFMailbox queueUpdateCountsForMailboxes:]_block_invoke_2 + 68
8 CoreFoundation 0x0000000111b81ea6 __65-[__NSDictionaryM enumerateKeysAndObjectsWithOptions:usingBlock:]_block_invoke + 102
9 CoreFoundation 0x0000000111b81db9 -[__NSDictionaryM enumerateKeysAndObjectsWithOptions:usingBlock:] + 217
10 Mail 0x000000010f41b0b6 __43+[MFMailbox queueUpdateCountsForMailboxes:]_block_invoke + 275
11 Foundation 0x000000010fb8d2e8 __NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__ + 7
12 Foundation 0x000000010fa79905 -[NSBlockOperation main] + 97
13 Foundation 0x000000010fa5859c -[__NSOperationInternal _start:] + 653
14 Foundation 0x000000010fa581a3 __NSOQSchedule_f + 184
15 libdispatch.dylib 0x0000000113ad5c13 _dispatch_client_callout + 8
16 libdispatch.dylib 0x0000000113ad9365 _dispatch_queue_drain + 1100
17 libdispatch.dylib 0x0000000113adaecc _dispatch_queue_invoke + 202
18 libdispatch.dylib 0x0000000113ad86b7 _dispatch_root_queue_drain + 463
19 libdispatch.dylib 0x0000000113ae6fe4 _dispatch_worker_thread3 + 91
20 libsystem_pthread.dylib 0x0000000113e136cb _pthread_wqthread + 729
21 libsystem_pthread.dylib 0x0000000113e114a1 start_wqthread + 13
1/2/2558 BE 7:14:27.597 PM Mail[941]: *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Absolute path passed into -[MFIMAPAccount mailboxForRelativePath:isFilesystemPath:create:]: /็Homeworks'
*** First throw call stack:
0 CoreFoundation 0x0000000111c5764c __exceptionPreprocess + 172
1 libobjc.A.dylib 0x000000010ffe26de objc_exception_throw + 43
2 CoreFoundation 0x0000000111c5742a +[NSException raise:format:arguments:] + 106
3 Foundation 0x000000010fb435b9 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 195
4 Mail 0x000000010f402f5c -[MFMailAccount mailboxForRelativePath:isFilesystemPath:create:] + 251
5 Mail 0x000000010f360404 -[MFIMAPAccount mailboxForRelativePath:isFilesystemPath:create:] + 491
6 Mail 0x000000010f404696 +[MFMailAccount mailboxForURL:forceCreation:syncableURL:] + 473
7 Mail 0x000000010f41b168 __43+[MFMailbox queueUpdateCountsForMailboxes:]_block_invoke_2 + 68
8 CoreFoundation 0x0000000111b81ea6 __65-[__NSDictionaryM enumerateKeysAndObjectsWithOptions:usingBlock:]_block_invoke + 102
9 CoreFoundation 0x0000000111b81db9 -[__NSDictionaryM enumerateKeysAndObjectsWithOptions:usingBlock:] + 217
10 Mail 0x000000010f41b0b6 __43+[MFMailbox queueUpdateCountsForMailboxes:]_block_invoke + 275
11 Foundation 0x000000010fb8d2e8 __NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__ + 7
12 Foundation 0x000000010fa79905 -[NSBlockOperation main] + 97
13 Foundation 0x000000010fa5859c -[__NSOperationInternal _start:] + 653
14 Foundation 0x000000010fa581a3 __NSOQSchedule_f + 184
15 libdispatch.dylib 0x0000000113ad5c13 _dispatch_client_callout + 8
16 libdispatch.dylib 0x0000000113ad9365 _dispatch_queue_drain + 1100
17 libdispatch.dylib 0x0000000113adaecc _dispatch_queue_invoke + 202
18 libdispatch.dylib 0x0000000113ad86b7 _dispatch_root_queue_drain + 463
19 libdispatch.dylib 0x0000000113ae6fe4 _dispatch_worker_thread3 + 91
20 libsystem_pthread.dylib 0x0000000113e136cb _pthread_wqthread + 729
21 libsystem_pthread.dylib 0x0000000113e114a1 start_wqthread + 13
1/2/2558 BE 7:14:31.133 PM com.apple.xpc.launchd[1]: (com.apple.ReportCrash[947]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.ReportCrash
1/2/2558 BE 7:14:31.482 PM diagnosticd[896]: error evaluating process info - pid: 941, punique: 941
1/2/2558 BE 7:14:33.551 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
1/2/2558 BE 7:14:49.406 PM mds[32]: (DiskStore.Normal:2376) 2a001 2.808408
1/2/2558 BE 7:15:01.570 PM hidd[72]: IOHIDEventQueue unable to get policy for event of type 11. (e00002e8)
1/2/2558 BE 7:15:01.577 PM hidd[72]: IOHIDEventQueue unable to get policy for event of type 11. (e00002e8)
1/2/2558 BE 7:15:01.586 PM hidd[72]: IOHIDEventQueue unable to get policy for event of type 11. (e00002e8)
1/2/2558 BE 7:15:01.594 PM hidd[72]: IOHIDEventQueue unable to get policy for event of type 11. (e00002e8)
1/2/2558 BE 7:15:01.602 PM hidd[72]: IOHIDEventQueue unable to get policy for event of type 11. (e00002e8)
1/2/2558 BE 7:15:01.610 PM hidd[72]: IOHIDEventQueue unable to get policy for event of type 11. (e00002e8)
1/2/2558 BE 7:15:01.626 PM hidd[72]: IOHIDEventQueue unable to get policy for event of type 11. (e00002e8)
1/2/2558 BE 7:15:01.633 PM hidd[72]: IOHIDEventQueue unable to get policy for event of type 11. (e00002e8)
1/2/2558 BE 7:15:01.641 PM hidd[72]: IOHIDEventQueue unable to get policy for event of type 11. (e00002e8)
1/2/2558 BE 7:15:01.665 PM hidd[72]: IOHIDEventQueue unable to get policy for event of type 11. (e00002e8)
1/2/2558 BE 7:15:01.673 PM hidd[72]: IOHIDEventQueue unable to get policy for event of type 11. (e00002e8)
1/2/2558 BE 7:15:01.682 PM hidd[72]: IOHIDEventQueue unable to get policy for event of type 11. (e00002e8)
1/2/2558 BE 7:15:01.689 PM hidd[72]: IOHIDEventQueue unable to get policy for event of type 11. (e00002e8)
1/2/2558 BE 7:15:05.659 PM com.apple.xpc.launchd[1]: (com.apple.mail.52288[941]) Service exited due to signal: Abort trap: 6
1/2/2558 BE 7:15:13.065 PM ReportCrash[947]: Saved crash report for Mail[941] version 8.1 (1993) to /Users/kulanak/Library/Logs/DiagnosticReports/Mail_2015-01-02-191512_apples-mac book-pro-3.crash
1/2/2558 BE 7:15:19.526 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
1/2/2558 BE 7:15:19.767 PM bird[859]: Assertion failed: ![_xpcClients containsObject:client]
1/2/2558 BE 7:15:19.767 PM bird[859]: Assertion failed: ![_xpcClients containsObject:client]
1/2/2558 BE 7:15:20.368 PM bird[859]: Assertion failed: ![_xpcClients containsObject:client]
1/2/2558 BE 7:15:25.817 PM Mail[951]: *** Assertion failure in -[MFIMAPAccount mailboxForRelativePath:isFilesystemPath:create:], /SourceCache/Mail/Mail-1993/MailFramework/Accounts/MFMailAccount.m:4467
1/2/2558 BE 7:15:25.819 PM Mail[951]: An uncaught exception was raised
1/2/2558 BE 7:15:25.819 PM Mail[951]: Absolute path passed into -[MFIMAPAccount mailboxForRelativePath:isFilesystemPath:create:]: /็Homeworks
1/2/2558 BE 7:15:25.820 PM Mail[951]: (
0 CoreFoundation 0x0000000111d3164c __exceptionPreprocess + 172
1 libobjc.A.dylib 0x00000001100c96de objc_exception_throw + 43
2 CoreFoundation 0x0000000111d3142a +[NSException raise:format:arguments:] + 106
3 Foundation 0x000000010fc285b9 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 195
4 Mail 0x000000010f4e2f5c -[MFMailAccount mailboxForRelativePath:isFilesystemPath:create:] + 251
5 Mail 0x000000010f440404 -[MFIMAPAccount mailboxForRelativePath:isFilesystemPath:create:] + 491
6 Mail 0x000000010f4e4696 +[MFMailAccount mailboxForURL:forceCreation:syncableURL:] + 473
7 Mail 0x000000010f4fb168 __43+[MFMailbox queueUpdateCountsForMailboxes:]_block_invoke_2 + 68
8 CoreFoundation 0x0000000111c5bea6 __65-[__NSDictionaryM enumerateKeysAndObjectsWithOptions:usingBlock:]_block_invoke + 102
9 CoreFoundation 0x0000000111c5bdb9 -[__NSDictionaryM enumerateKeysAndObjectsWithOptions:usingBlock:] + 217
10 Mail 0x000000010f4fb0b6 __43+[MFMailbox queueUpdateCountsForMailboxes:]_block_invoke + 275
11 Foundation 0x000000010fc722e8 __NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__ + 7
12 Foundation 0x000000010fb5e905 -[NSBlockOperation main] + 97
13 Foundation 0x000000010fb3d59c -[__NSOperationInternal _start:] + 653
14 Foundation 0x000000010fb3d1a3 __NSOQSchedule_f + 184
15 libdispatch.dylib 0x0000000113bbac13 _dispatch_client_callout + 8
16 libdispatch.dylib 0x0000000113bbe365 _dispatch_queue_drain + 1100
17 libdispatch.dylib 0x0000000113bbfecc _dispatch_queue_invoke + 202
18 libdispatch.dylib 0x0000000113bbd6b7 _dispatch_root_queue_drain + 463
19 libdispatch.dylib 0x0000000113bcbfe4 _dispatch_worker_thread3 + 91
20 libsystem_pthread.dylib 0x0000000113f0f6cb _pthread_wqthread + 729
21 libsystem_pthread.dylib 0x0000000113f0d4a1 start_wqthread + 13
1/2/2558 BE 7:15:25.821 PM Mail[951]: *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Absolute path passed into -[MFIMAPAccount mailboxForRelativePath:isFilesystemPath:create:]: /็Homeworks'
*** First throw call stack:
0 CoreFoundation 0x0000000111d3164c __exceptionPreprocess + 172
1 libobjc.A.dylib 0x00000001100c96de objc_exception_throw + 43
2 CoreFoundation 0x0000000111d3142a +[NSException raise:format:arguments:] + 106
3 Foundation 0x000000010fc285b9 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 195
4 Mail 0x000000010f4e2f5c -[MFMailAccount mailboxForRelativePath:isFilesystemPath:create:] + 251
5 Mail 0x000000010f440404 -[MFIMAPAccount mailboxForRelativePath:isFilesystemPath:create:] + 491
6 Mail 0x000000010f4e4696 +[MFMailAccount mailboxForURL:forceCreation:syncableURL:] + 473
7 Mail 0x000000010f4fb168 __43+[MFMailbox queueUpdateCountsForMailboxes:]_block_invoke_2 + 68
8 CoreFoundation 0x0000000111c5bea6 __65-[__NSDictionaryM enumerateKeysAndObjectsWithOptions:usingBlock:]_block_invoke + 102
9 CoreFoundation 0x0000000111c5bdb9 -[__NSDictionaryM enumerateKeysAndObjectsWithOptions:usingBlock:] + 217
10 Mail 0x000000010f4fb0b6 __43+[MFMailbox queueUpdateCountsForMailboxes:]_block_invoke + 275
11 Foundation 0x000000010fc722e8 __NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__ + 7
12 Foundation 0x000000010fb5e905 -[NSBlockOperation main] + 97
13 Foundation 0x000000010fb3d59c -[__NSOperationInternal _start:] + 653
14 Foundation 0x000000010fb3d1a3 __NSOQSchedule_f + 184
15 libdispatch.dylib 0x0000000113bbac13 _dispatch_client_callout + 8
16 libdispatch.dylib 0x0000000113bbe365 _dispatch_queue_drain + 1100
17 libdispatch.dylib 0x0000000113bbfecc _dispatch_queue_invoke + 202
18 libdispatch.dylib 0x0000000113bbd6b7 _dispatch_root_queue_drain + 463
19 libdispatch.dylib 0x0000000113bcbfe4 _dispatch_worker_thread3 + 91
20 libsystem_pthread.dylib 0x0000000113f0f6cb _pthread_wqthread + 729
21 libsystem_pthread.dylib 0x0000000113f0d4a1 start_wqthread + 13
1/2/2558 BE 7:15:26.815 PM com.apple.xpc.launchd[1]: (com.apple.mail.52288[951]) Service exited due to signal: Abort trap: 6
1/2/2558 BE 7:15:26.892 PM ReportCrash[947]: Saved crash report for Mail[951] version 8.1 (1993) to /Users/kulanak/Library/Logs/DiagnosticReports/Mail_2015-01-02-191526_apples-mac book-pro-3.crash
1/2/2558 BE 7:15:26.904 PM ReportCrash[947]: Removing excessive log: file:///Users/kulanak/Library/Logs/DiagnosticReports/Mail_2015-01-02-061109_app les-macbook-pro-3.crashTry a restart.
Do a backup, using either Time Machine or a cloning program, to ensure files/data can be recovered. Two backups are better than one.
Try setting up another admin user account to see if the same problem continues. If Back-to-My Mac is selected in System Preferences, the Guest account will not work. The intent is to see if it is specific to one account or a system wide problem. This account can be deleted later.
Isolating an issue by using another user account
Try booting into the Safe Mode using your normal account. Disconnect all peripherals except those needed for the test. Shut down the computer and then power it back up after waiting 10 seconds. Immediately after hearing the startup chime, hold down the shift key and continue to hold it until the gray Apple icon and a progress bar appear and again when you log in. The boot up is significantly slower than normal. This will reset some caches, forces a directory check, and disables all startup and login items, among other things. When you reboot normally, the initial reboot may be slower than normal. If the system operates normally, there may be 3rd party applications which are causing a problem. Try deleting/disabling the third party applications after a restart by using the application un-installer. For each disable/delete, you will need to restart if you don’t do them all at once.
Safe Mode - About
Safe Mode - Yosemite -
Problem with mail after upgrading to tiger...
When I upgraded the OS in my PowerBook, all the mail messages in my in-box disappeared. Now, the only thing that shows up in each mail is the following, "The message from [Antonio john Doe <[email protected]>] concerning “Stuff” has not been downloaded from the server. You need to take this account online in order to download it."
The e-mail is also gone from the earthlink
server because they wipe all mail out after a few days. Is there a
way to recover the messages?
Powermac G5 dual 1.8 Mac OS X (10.4.6) 1.3 Gb ramThe conversion from Mail 1.x to Mail 2.x is broken. Take a look at the following thread to better understand the problem:
Help! "You need to take this account online in order to download it."
More specifically, if this is a POP account, the following procedure should allow you to fix the Inbox problem. A similar procedure should allow you to fix other mailboxes that might also be affected:
1. Quit Mail if it’s running.
2. Make a backup copy of the ~/Library/Mail folder, just in case something goes wrong while trying to fix the problem. You can do this in the Finder by dragging the folder to the Desktop while holding the Option (Alt) key down, for example. This is where all your mail is stored.
3. Create a new folder on the Desktop and name it however you wish (e.g. Inbox Old). It doesn’t need to have an .mbox extension.
4. In the Finder, go to ~/Library/Mail/POP-username@mailserver/INBOX.mbox/.
5. Move the files mbox and Incoming_Mail out of INBOX.mbox, into the Inbox Old folder just created on the Desktop. These files contain all the messages that were in the mailbox before the upgrade to Tiger, and maybe even some messages that had been deleted. mbox is the most important. Incoming_Mail may or may not be present.
6. Move any strangely-named Messages-T0x... folders to the Desktop (not into the Inbox Old folder). These folders are to be deleted after fixing the problem. They are temporary folders created during an import or an indexing process, and Mail should have deleted them when done. Their presence is a clear indication that something didn’t work as expected. If you’ve been using Mail after the conversion and have already tried to fix the problem by rebuilding the mailbox or something like that, they might contain messages that are neither in Messages proper nor in the mbox file, so keep them around until the problem is fixed.
7. Move everything else within INBOX.mbox, except the Messages folder, to the Trash.
The result of the above should be that INBOX.mbox contains the proper Messages folder only, and the Inbox Old folder on the Desktop contains the mbox and Incoming_Mail (if it exists) files only. Now, proceed as follows:
8. Open Mail.
9. The account’s Inbox should properly display in Mail as many messages as *.emlx files are in ~/Library/Mail/POP-username@mailserver/INBOX.mbox/Messages/. If that’s not the case, select the mailbox in Mail and do Mailbox > Rebuild.
10. In Mail, do File > Import Mailboxes, choose Other as the data format, and follow the instructions to import the Inbox Old folder that’s on the Desktop.
As a result of doing the above, some messages may be duplicated now. Andreas Amann’s Mail Scripts has a Remove Duplicates script that you may find useful for that.
Do with the imported mail whatever you wish. You may move the messages anywhere you want and get rid of the imported mailboxes afterwards.
If all is well and you don’t miss anything, the files on the Desktop can be deleted, although you may want to keep them for a while, just in case.
You may want to take a look at the following article (also referenced in the thread I mentioned at the beginning of this post) to learn what you might have done before upgrading to minimize the risk of this happening, and what you may do after fixing the problem to avoid similar issues from happening in the future. DON’T do now what the article suggests, though, as that would make things worse in the current situation:
Overstuffed mailbox is unexpectedly empty
Ask for any clarifications or if you need further assistance.
Note: For those not familiarized with the ~/ notation, it refers to the user’s home folder, i.e. ~/Library is the Library folder within the user’s home folder. -
Inbound Idoc processing issues - Partner Profiles - error status 56
Hello All,
I'm having a little difficulty posting an idoc coming from MDM. It's a CREMDM04 xml coming from an MDM system. It is getting mapped through PI and is being split into ADRMAS02 and CREMAS04 Idocs. The message is being passed through XI and being posted to the ECC system, but certain fields in the EDI_DC40 header table are not being populated correctly (i believe). I'm using nothing but standard mapping/material from the SAP Business Content for XI. After looking through the standard XSLTs i cannot find the field-to-field mapping where the fields below are being populated.
The RCVPOR value (SAP[SID]) is correct when i view it in SOAP Header, but does not appear in the remote system under the receiver port for the inbound idoc.
The RCVPRN value ([String Value]) is incorrect in the SOAP Header and does appear in the remote system under the receiver partner number for the inbound idoc. How is the RCVPRN value being populated?
SOAP Header in IDocOutbound tag
<SAP:RCVPOR>SAP[SID]</SAP:RCVPOR>
<SAP:RCVPRN>[String Value]</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
I've been trying to trace down the string value for the RCVPRN, but i cannot find it anywhere. Perhaps i'm just overlooking it?
When i set the proper values (port = SAP<SIDofECC> and partner number = <LSnameof ECC>) using WE19 in the remote system then the partner profile is found and i'm left with different error to please specify an address group.
Any help is very much appreciated! :-DHi Jason ,
Just check out if you have done the following steps most of us make minor mistake here ....... I think this would solve your problem
To Configure the IDOC SCENARIOS ,PROCEED AS FOLLOWS
STEP 1:ALE SETTINGS TO POST IDOC INTO SAP R/3
We need to do the following settings in XI
1) Create an RFC Destination to the Receiving System in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a) Select Create New button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client
d) Enter the RFC Destination created in XI towards R/3
e) Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) Create an RFC Destination to XI in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Inbound Parameters (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Inbound Parameters.So click on ADD TO Create Inbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Message Type and Process Code.
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
do let me know if it helped
Edited by: Tom Jose on Feb 21, 2008 9:04 AM -
How to trigger an E-mail after saving a Case
Dear all,
We need to trigger an action to send an E-mail after creation and saving a Case in EP.
Please help me how could we configure this in the system.
Your suggestions will be highly appreciated.
Best wishes
Raghu ramHi Raghu,
By using he action profile you can trigger the email once you save the transaction.
We have processing types in action profile,
1.Immediate
2.Recurring
3.After saving
In ur case you can after saving the document.
and assign the action profile to the transcation type.
Regards
Chandramohan -
we have a requirement where in we need to post invoice using idoc_input_invoic_mrm FM (coming as INVOIC02 IDoc) and once posted successfully, immediately clear the document using F-53..
What is the best approach to do this?
1) clone IDOC FM and call BAPI to post F-53? Do we need to issue COmmit work before F-53 to ensure that invoice posting is commited?
Or this is not feasible?Generally inbound IDocs handler FM is called by number of ALE layer FMs which manage also commit to data base.
The call stack for immediate IDoc processing:
- program RBDAPP01
- FM APPLICATION_IDOC_POST_IMMEDIAT
- IDOC_START_INBOUND
- IDOC_INPUT
-- form IDOCS_PROCESS (here customizing is resolved and actual IDoc handler FM is dynamically called)
--- FM TRANSACTION_END with actual COMMIT WORK
This is an example which shows that you have to do your own commit after calling IDOC_INPUT_INVOIC_MRM and before document clearing. In addition all "create" routines inside IDOC_INPUT_INVOIC_MRM are called with addition ON COMMIT - so actual commit is out of control of IDOC_INPUT_INVOIC_MRM.
Regards,
Maxim. -
Tables updated after IDOC posting
Hi All,
I am having a requirement in which I am using a custom function module to create and post an IDOC. The program is taking data from flat file and passing it to the function module IDOC_INBOUND_SINGLE which calls a BAPI BAPI_ACC_INVOICE_RECEIPT_POST to post the IDOC.
For posting IDOCS, IDOC type ACC_INVOICE_RECEIPT03 is being used.
I wanted to know after execution of the FM, which are the tables being updated after posting of IDOC.
Thanks in advance.
regards,
gauravYOu can do a trace to find all the tables that get updated.
Go to ST05 transaction.
Start the trace.
Run your inbound IDOC process.
Go to ST05 again and decativte the trace.
View the trace to find the tables that are Updated.
Regards,
Ravi -
Hi,
I have to create new program for Mail after Goods Receipt (external email).
Plesae let me know any suggestion for this requrement.
Thanks in advance.Hi All,
Can any one give me any hint regarding this reuirement.
I have to write a program once we receive the goods an email has to generate.
i have to use text_wemail_fuellen text rotine which is in standard program SAPMM7M:
But i have copied this routine & modify accoeding to my requirement.
i am not getting the message text table .please let me know the table name also.
i have craeted new output types & processing sequence .
Regards.
PS -
Data transfer between SAP & Java and Vice versa using IDOC Process
Dear Experts,
We are working on one of the good requirement related to data transfer between SAP and Java software. Client requirement is, they want to transfer the data in both the ways (from SAP --> Java and Vice versa also).
In detail is, after sales order creation using one custom program loading plan details will be calculated. Once loading dates are confirmed then, user will release the sales document to transfer the data from SAP to Java using "Outbound IDOC processing". Similarly in that JAVA software some shipment details will be performed, once completed from JAVA software again details needs to be pumped back to SAP as "Inbound IDOC Processing".
For this fields are already identified from external software SAP and we are looking for the same to perform the steps in SAP.
At this stage, I need your expert opinion / feedback how to go about at this stage.
Meaning,
1. What are the customizing steps needs to be done in SAP..?
2. How to trigger the :Outbound IDOC process" once the documents are "Released" from custom transaction
3. How to create the link between SAP and JAVA to transfer the data between these 2 software
4. How to trigger the "Inbound IDOC Process" from JAVA software to SAP and how to store the data in SAP
Experts, please give your feedback in terms of reply or by sending the step by step process to fulfill this client requirement.
Thanks for your cooperation.
Regards,
RameshMaybe too many open questions in the same document.
Maybe you should repost a more specific question in a technical forum.
This looks like a small project where you already know what you want, maybe you should contract a technical specialist so he proceeds to the implementation! -
gud mrng,
after creating the idoc function module,how are we writing the code?
how are we using the standard idoc?Hi Priya ,
Check this .....
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
Reward if useful.
Regards,
Chitra -
Hi all,
I am working on an IDOC process that will list the idocs in error which are ready for reprocessing. when I execute this custom transaction it will give me the list of all the idoc numbers with status E i.e. error, when i fix the error and want to reprocess the error it shows me a screen which says
Reprocess Idoc's
and it says "Call Transaction processing" with following radio buttons:
1. In background
2. In foreground
3. In foreground after error.
My functional folk wants to set this radio button as default to In the foreground, so can you please tell me how I can acheive this.
Thanks,
Rajeevwhen i process the idoc the start time screen shows after job,after event,at operation mode
does its easy to process the idoc by using this methods and also to schedule.
Maybe you are looking for
-
Updating CS5 Bridge too work with a new camera Canon EOS 70D
Can someone please help me with how I could update my version of Bridge ?
-
Problem in periodic job scheduling in LBWE
hi, i have activated the Material movements datasource 2LIS_03_BF. Filled up the set up table. now when i try to schedula a job in jobcontrol, under the tab *immediate* the immediate start check box is checked and disabled. the periodic job check bo
-
Does for upgrade from ecc 5.0 to ecc 6.0 we have to pay money for that
Hi All Does for upgrade from ecc 5.0 to ecc 6.0 we have to pay money to SAP for that.
-
Hi, having problems importing titles from livetype into final cut studio. Ive created the titles with no problem and rendered them in LT but when I import into FCS I get a blank screen with unrendered right across the middle. What am I doing wrong???
-
Oracle SupplyChain Management module(Manufacturing) Training in Hyderabad
Hi all, Could anyone give me any information on where one can obtain training on Oracle SupplyChain Management module(Manufacturing) Training in Hyderabad? I enquired at various institutes like Orapps,Appsworld,Compulearn,Genesis etc but they either