Idoc PEXR2002 Message User Guide

Hi, I am looking at creating a message map with PAYEXT as one of the message interface. I would like to know where I can get the documention on the Idoc Message Type.
For Example: IDDAT is a qualifier with several values. Where can I get the complete set of values and their purpose?
<E1EDK03 SEGMENT="1">
     <IDDAT>011</IDDAT>
     <DATUM>20080128</DATUM>
     <UZEIT>143119</UZEIT>
</E1EDK03>
<E1EDK03 SEGMENT="1">
     <IDDAT>028</IDDAT>
     <DATUM>20080128</DATUM>
</E1EDK03>
<E1EDK03 SEGMENT="1">
     <IDDAT>017</IDDAT>
     <DATUM>20080128</DATUM>
</E1EDK03>
Thanks

Hi,
>>>For Example: IDDAT is a qualifier with several values. Where can I get the complete set of values and their purpose?
there is another way to check it
open transaction WE19
put the name of the IDOC there and run the transaction
then find the segment which contains the qualifier you're looking for
and press F4 to get a list with values and descriptions
Regards,
Michal Krawczyk

Similar Messages

User guide: MSI HQ USB BIOS Flash Tool

Guide based on USB tool v1.17c
HOW TO properly use the MSI Forum HQ USB Flashing Tool to update your BIOS
This user guide provides a step-by-step explanation for properly using the >>MSI Forum HQ USB Flashing Tool<< to prepare a USB Flash Drive for a safe BIOS-Flash in a pure DOS Environment. The tool itself will not perform the actual flashing operation. It will "only" help you to get your USB Stick set up for an automated DOS flashing procedure which requires final confirmation. (If you should run into any problems before you are prompted for final confirmation in DOS, no attempt to flash has been made yet and there is no danger of a bad flash.)
NOTE: If you are having problems getting your USB device to boot correctly, you may need to format it correctly as the geometry data may be incorrect. You can do that by pickup option "Fix My USB key" from the Tool or by using >>> THIS <<< tool here! For future usage you can skip this step, it need to be done only once if your stick need adjustment.
Symptoms that your USB key need a fix after booting from the USB key:
* Error: "No bootable partition in table"
* Blinking cursor in a top left corner and nothing happens
* "RIVER2 MSI"
* "Error loading operating system"
* "Missing operating system"
* "Disk in drive is not a bootable"
* Booting from selected USB key is IGNORED, the other/typical OS continue to load as usual
If still no change after using "Fix My USB key" Tool's option or HP Formatter Tool as alternative.
Then try with different USB key, the issue is there.
Note: Those USB keys who support "U3 Smart", this "feature" must be removed before proceed.
Refer to followed link: http://u3.sandisk.com/launchpadremoval.htm
Read the three notes that follow first before you move on:
1. Note: Before you even think about flashing a different BIOS, be sure that your system is stable. If it is not stable, make it stable first. (Read >>here<<.)
2. Note: Make sure your system meets the preconditions and system requirements mentioned below before you attempt to use the tool.
3. Note: Do know that flashing your BIOS, be it with the help of the tool or otherwise, is done at your own risk.
Contents of the Guide:
0. Preconditions & System Requirements
1. Basic Description of Functionality
2. Installing/Starting the tool.
3. Choosing a Preparation Method
3.1. Method 1: Processing a BIOS Archive Directly (ZIP/RAR)
3.2. Method 2: Processing a BIOS File Directly
3.3. Method 3: SureHands Live Update
3.4. Method 4: Geometry Change
4. Selecting the USB Flash Drive for preparation
5. BIOS Settings, Booting & Flashing
5.1. BIOS Settings to Check
5.2. Booting from USB Flash Drive
5.3. Flashing Procedure/Running MemTest86+ & CMOS-Clear
6. FAQ: Common Problems & Solutions
7. Version History
0. Preconditions & System Requirements
The main precondition for using the tool is a working & healthy Windows installation on the system that needs the BIOS flash. The Tool is designed to work with MSI Retail Boards & Laptops only.
Please note mainboards of other brands and OEM boards that are manufactured by MSI but sold by Medion, HP, NEC and others are not supported. If you have an OEM board that needs a BIOS update read this topic: >>OEM boards manufactured by MSI<<
Supported Operating Systems: All current Windows Versions (32bit & 64bit, any service pack (SP)): Windows NT, Windows 2000, Windows 2003, Windows XP, Windows Vista, and Windows 7.
The second requirement is that you have a fully functional USB Flash Drive that uses the FAT file system (FAT/FAT32). NTFS is not supported. If your USB Flash Drive is using the NTFS File System, reformat it to FAT or FAT32.
As the tool also provides a Live Update Option ("SureHands"), you'll need a working internet connection if you want to choose this method. Not all boards are supported at this point.*
* Check section 3.3 of this guide to see if your board is currently supported by the SureHands feature.
1. Basic Description of Functionality
The MSI Forum HQ USB Flashing Tool will help you to easily prepare an USB flash drive for an automated BIOS flash in a pure DOS environment, which is the safest way to perform such a procedure. The tool will also allow you to run MemTest86+ in a pure DOS environment. However, the preparation of your USB Stick is done in Windows and basically includes two steps:
(1) The device will be made bootable.
(2) All necessary files (incl. BIOS file, actual flasher and MemTest86+ executable) and all DOS commands that are needed to flash/test memory will automatically be implemented.
Because the tool does not reformat your USB Flash Drive*, no files that may currently be on the stick will be lost during the procedure. Just make sure that there is still some free drive space, otherwise there will not be enough room for the files that are needed for BIOS Flashing.
* Excluding the Geometry Change method which will destroy all data on the USB storage device.
2. Installing/Starting the tool
Treat the forum's USB Flashing Tool like a regular application. Download it to and run it from your hard drive, there is no need to copy & start it from the USB Flash Drive that you want to use for flashing. Both, the installer version and the stand-alone version, do precisely the same job. Which of the two versions you use, is solely up to you and your preferences. The stand-alone version can be started directly by clicking on the executable file. The installer version will perform an installation and provide you with an entry in your start menu and a desktop shortcut to start the tool.
When you start the tool a DOS box should open up to provide you with status messages and prompts. Do not close that box unless you want to abort the preparation procedure!
Please ensure that you connect the USB flash drive you wish to use before starting the Tool!
NOTE: If you do not connect your USB storage device before starting the tool, or the tool doesn't detect it. You can still insert the drive letter, as the tool will continue as normal.
The tool will first check, if an MSI mainboard is installed in your system and show you its model name and PCB Version in a message box. Click >OK< to continue to choose the tool's preparation method that you want to use to prepare your USB Flash Drive.
3. Choosing a Preparation Method
If your MSI Retail Board is properly detected and you have pressed the >OK< button in the message box, an option box will pop up that allows you to choose between three different operating modes. The options you can choose from are more or less self-explanatory, however, read the detailed description if you are unsure how to proceed at this point:
3.1. Method 1: Processing a BIOS Archive Directly (ZIP/RAR)
Official MSI BIOS-Updates that can be downloaded from the product site of your board model do usually come as .ZIP or .RAR archives that contain the actual BIOS File and the corresponding AWARD or AMI flashing utility (depending on the BIOS Type of your board). If you have downloaded such an archive, you should choose the first method from the option box.
You do not need to extract the files from the BIOS archive. The tool will ask you to point it to the archive you downloaded and automatically extract the BIOS File and the AMI or AWARD flashing utility and put it them on your USB Flash Drive. You don't have to worry about anything else. All you have to do is to remember where you saved the ZIP or RAR file you downloaded:
3.2. Method 2: Processing a BIOS File Directly
If you do not have a ZIP or RAR archive that already contains a BIOS File and the proper flashing utitility, but only the plain unpacked BIOS File, choose the second Method from the option box. In most cases BETA BIOS Files supplied by MSI Support or shared here in the Forum do not come with the proper flashing utility. If the MSI Forum HQ USB Flashing Tool is told to process a plain BIOS File, it will automatically check the type of BIOS File (AMI or AWARD) and then select the proper flashing utility that needs to be used. All you need to do is point the tool to the BIOS-File that is supposed to be flashed:
3.3. Method 3: SureHands Live Update
"SureHands Live Update" is the third operation method you can choose from the option box. It provides a much safer and more reliable alternative to MSI Live Update as the actual BIOS Flash is performed in a pure DOS environment as well. If you decide to use this option, you do not to supply the tool with a BIOS-Archive or a BIOS-File.
Not all MSI Retail Boards are currently supported. With every update of the USB Flashing Tool more boards will be added. At present, you can use the "SureHands" Live Update method with the following boards only (the list will be updated regularly):
AMD based boards:
K8N Neo4-F (MS-7125, PCB 3.0)
K8NGM2-FID (MS-7207, PCB 2.0)
K8N Diamond Plus (MS-7220, PCB 1.0)
K8N Neo3 (MS-7135, PCB 1.0 & 2.0)
K9A Platinum (MS-7280, PCB 1.0)
K9A2 Platinum (MS-7376, PCB 1.0)
K9A2 CF-F (MS-7388, PCB 1.0)
K9N Neo-F (MS-7260, PCB 1.0 & 2.0)
K9VGM-V (MS-7253, PCB1.0)
K9N2GM-F V2 (MS-7509, PCB 1.0)
K9N Neo V2 / V3 (MS-7369, PCB 1.1)
K9N Platinum & K9N SLI Platinum (MS-7250, PCB1.0)
K9N2 Diamond (MS-7375, PCB 1.1)
K9N2 SLI Platinum (MS-7374, PCB 1.1)
K9N2 Zilent (MS-7374, PCB 1.1)
K9N2 Neo-F (MS-7511, PCB 1.1)
DKA790GX Platinum (MS-7550, PCB 1.1)
790FX-GD70 (MS-7577, PCB 1.0)
790GX-G65 (MS-7576, PCB 1.0)
Intel based boards
HydroGenX48C & X48C Platinum (MS-7353, PCB 3.0)
X48 Platinum (MS-7353, PCB 1.0)
X38 Diamond Plus
X38 Diamond (MS-7353, PCB 1.0)
X38 Platinum (MS-7353, PCB 1.0)
EFINITY-FP (MS-7395(E), PCB 1.0)
P35 Neo Combo-F (MS-7365, PCB 1.0)
P35 Neo2 Series (MS-7345, PCB 1.1)
P35 Platinum (MS-7345, PCB 1.1)
P35 Neo-F (MS-7360, PCB 1.0)
G33 Platinum (MS-7345, PCB 1.1 & PCB 1.2)
P965 Platinum (MS-7238, PCB 1.1)
975X Platinum PowerUp Edition (MS-7246, PCB 2.1)
865PE Neo2-P Platinum Edition (MS-6728, PCB 2.0C)
P7N SLI Platinum (MS-7380, PCB 1.0)
P7N2 Diamond (MS-7523 PCB 1.0)
P7N Diamond (MS-7510, PCB 1.0)
P7N SLI Platinum (MS-7380, PCB 1.0)
P6N Diamond (MS-7320, PCB 1.0)
P6N SLI Platinum (MS-7350, PCB 1.0)
P6N SLI-FI (MS-7350 PCB 2.0)
P6N SLI V2 (MS-7346 PCB 1.0)
ECLIPSE SLI (MS-7520, PCB 1.0)
ECLIPSE Plus (MS-7566, PCB 1.0)
P35 Neo3-F (MS-7395, PCB 1.0)
After selecting "SureHands" from the option box, the tool will automatically check for all available official BIOS-Versions for your mainboard. It will also look for the latest available BETA BIOS Version for you board and save that information in a TXT-File on your Desktop:
Note: The SureHands option will not provide you with the latest BETA BIOS, it will only provide the information.
When the tool is done scanning for official BIOS releases for your board, it will give you the possibility to manually choose the BIOS Version you want to flash. SureHands Live Update will not automatically select the latest version and use it for flashing, it will give you the chance of choosing between all available official BIOS releases that are available:
Note that the "May not exist" comment that appears behind some versions does not mean that the BIOS does not exist. If you know the latest BIOS for your board is e.g. v1.8, SureHands will retrieve it even though there may be such a comment. That message is part of a prediction feature that tries to determine future BIOS Releases. If a BIOS version that was predicted by the SureHands feature is not available yet, the tool will tell you if it cannot retrieve the files and ask you to select an earlier version.
3.4 Geometry Change
If the tool fails to make your USB storage device bootable then you will need to use this mode. It will make your drive bootable, select it:
Select your drive then let the tool do it's business.
Once the process is complete, run the tool again via method 1, 2 or 3, restart your computer and try booting from the USB storage device again.
NOTE: This method will destroy ALL data on the USB storage device!
NOTE: This method is available in v1.17 and beyond.
4. Selecting the USB Flash Drive for preparation
When you have chosen one of the three methods from the option list and pointed the tool at the corresponding archive, BIOS File or selected the desired BIOS Version from the list in case you chose to use SureHands Live Update, the MSI Forum HQ USB Flashing Tool will prompt you to enter the drive letter of the USB Flash Drive you want to use for flashing:
Note that certain drive letters are reserved and will therefore not be accepted by the tool (currently A:, B: and C:). If you are sure you have connected an USB Flash Drive to the system that works properly but it does not appear in the table that appears in the DOS box, enter the corresponding drive letter anyway and see if the tool accepts it. This can happen in rare cases, but it is usually no problem.
The tool will check the selected drive and will provide you with status messages. If everything is okay, the message should look like this:
The tool will attempt to make the device bootable and automatically write all files that are needed for flashing to the drive to prepare it for flashing. If the procedure was successful, you will get the following message in the DOS box:
5. BIOS-Settings, Booting & Flashing
If the Tool has prepared your drive for booting & flashing, no BIOS flash attempt has been made yet. Only the preparation process. In order to initiate the flashing procedure, you have to restart your system and make it boot from the USB Flash drive. Before you move on to do that, enter the BIOS Setup and check a few options:
5.1. BIOS Settings to Check
Check USB-related Options in BIOS:
- USB Controller
- USB 2.0 Controller
- USB Legacy Support
- USB Storage Support
- Boot from other devices
- etc.
Not all of these options may be found in BIOS and the precise name may vary as well. Just make sure you checked for such options and that they are enabled (if present).
Another option you should check for is "Boot Sector Protection". If such an option is present in your BIOS, make sure it is disabled because it may make a BIOS Flash impossible.
@all Overclockers: In case your system is currently overclocked, make sure you roll back to default clock and voltage settings before you attempt to start the flashing procedure. Otherwise you increase the risk of an unsuccesful flash, and you most probably don't want something like that to happen.
5.2. Booting from USB Flash Drive
To boot from your USB drive you can either change the boot sequence in BIOS accordingly or just press F11 during POST* to get access to the BIOS Boot Menu. From here, you can select you drive directly without having to adjust the boot sequence in BIOS. Note that your USB Flash Drive may be listed as a hard drive (if you choose that entry you will get another list to choose from).
* Not all mainboards use F11, for the boot menu. If F11 fails for you, please consult your manual for the correct key.
Note: If you have problems booting from your drive, look at the FAQ-Section of this guide and see if any of the tips resolve the issue.
5.3. Flashing Procedure/Running MemTest86+
As soon as the system boots from the drive, DOS will be loaded and you will be displayed with two options. One option will start MemTest86+, the other will begin the flashing procedure. If no choice is made, MemTest86+ will automatically start.
The flashing procedure will automatically be initiated from there. You will see status messages on the screen that will supply you with information and also prompt you for final confirmation for the actual BIOS-Flash. A backup of you current BIOS will automatically be saved to a file on the drive (backup.bin) before the flashing actually starts. You do not need to enter any commands in DOS. All you have to do is acknowledge the information on the screen by pressing a key.
The flash itself will only take a couple of seconds (20-30s at the most). If the flashing is successfully completed, shutdown the system and clear CMOS with main A/C power cable removed from PSU. Read the >>Clear CMOS Guide<< for further information.
After clearing CMOS you have completed the BIOS-Flash.
Guide created by Jack The Newbie and the forum team

Version updated to 1.18x:
* Mode 3 Sure Hands, Live Update:
- Removed beta BIOS query check[global]
- Fixed issue K9N2 Diamond unable to be detected as supported unit if onboard is installed BIOS version 2.4,
add dynamic detection for future versions.
- Fixed issue 790FX-GD70 unable to be detected as supported unit and add dynamic detection for future versions.
- Fixed issue 790GX-G65 unable to be detected as supported unit and add dynamic detection for future versions.
- Add support for 785G-E65, add dynamic detection for future versions, prediction BIOS range 3.1 - 3.A
- Add support for 785G-E53, add dynamic detection for future versions, prediction BIOS range 3.1 - 3.A
- Add support for 790GX-G65 Winki ED, prediction BIOS range 2.1 - 2.A
- Fixed issue P7N Diamond unable to be detected as supported unit if onboard BIOS installed is 1.3 and above,
add dynamic detection for future versions.
- Add support for K9A2 Neo2, prediction BIOS range 7.4 - 7.D
- Add support for 790XT-G45, prediction BIOS range 2.2 - 2.B
- Add support for 770T-C45, prediction BIOS range 8.4 - 8.D
- Add support for 770T-C35, prediction BIOS range 8.4 - 8.D
- Fixed issue K9A2 Platinum[V1,V2] unable to be detected as supported unit if onboard BIOS installed is 1.9,
add dynamic detection for future versions, prediction BIOS range extended to 1.F0
- 790GX-G65 board prediction BIOS range extended to ver: 1.D0
- 790GX-G65 board update bios base ver from 1.xx to 4.xx [following new msi rule for this board jumping from 1.xx to 4.xx]
- Add support for 770-C35|C45 boards [p1] BIOS range 1.40 - 1.D0
- Add support for 770-G45 board [p2] BIOS range A10 - AA0
* Add "Exit" option to navigation screen
* Update version info related to boot part
* Update boot part to handle newest features
* Modify Self update sequence of Installer version
* Update internal version check ID
* Mode 4 minor update
* Build and add new Tool's module for newest features
* W32 Tool's exit time part decreased by 10 seconds
* On received OS reboot user request, time delay before execution decreased by 15 seconds
* Update EC decoder
* Update start-up information screen
* Auto store start-up detected information to user's desktop ==> [MSIHQ_INFO.TXT]
Details:
Easy to show machine information on request, instead write down from the screen manually, now just copy/paste can be used from MSIHQ_INFO.TXT
User can check and compare information before and after the BIOS update
Also usefull if didn't remember what was his original BIOS or EC versions before the update, Tool will auto store it there.
And easy can be checked if needs. E.g Tool's log file of each Tool's execution, each report will include date and time as well.
F.A.Q example:
Q: I flashed BIOS on my notebook and now it doesn't work properly.. And i don't remember what was my old BIOS version.. What can i do?
A: Take a look in MSIHQ_INFO.TXT at your desktop, there is auto recorded your detailed information about your notebook before the BIOS update.
So you can easy find what was your original BIOS & EC versions.
Is it OEM one or not, and the exact original BIOS & EC versions.
So you can roll back easy or if crossflashing were done to reflash to correct versions.
Example question:[this board now use 4.xx bios, but don't have time to make a new images.]
It's just example, do not mean that this BIOS used in the example is bad. But generally often can need to roll back to older version.
Or to use Sure Hands because[The BIOS is N/A for manual download, By SureHands no need to browse/search/download and point to the BIOS version, also eliminate any chances to pickup the wrong BIOS, and not at last its more quickly[save a time]]
Q: I flashed my BIOS via MSI Live Update, but the new BIOS has an issues.
How i can roll back to my old BIOS version?
The MSI LiveUpdate can only update to the latest BIOS version, which is not good for me.
And i can't download my old BIOS version manually... Because "This BIOS can only update via Live Update function"
http://eu.msi.com/index.php?func=downloaddetail&type=bios&maincat_no=1&prod_no=1739
How i can re-flash to my original BIOS version and from where can i get it?
A: Run >>Use the MSI HQ Forum USB flasher<<,
then choose Mode 3 [Live Update{aka SureHands}]:
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in ба 30.12.2009 Ј. at 21:09:45,15
Mainboard: 790GX-G65 (MS-7576)
PCB Version: 1.0
BIOS Version: V1.3
BIOS Date: 05/08/2009
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in ба 30.12.2009 Ј. at 21:22:38,42
Mainboard: 790GX-G65 (MS-7576)
PCB Version: 1.0
BIOS Version: V1.6
BIOS Date: 11/30/2009
Then choose your old BIOS version from the list:
The followed image used below is a sample from Eclipse board,[no time to make accurate image] but will look similar for others boards too:
In a list will be noticed that there is a future BIOS versions.
Some of them will be not released yet. If you pick some of those the Tool will note you:
It's a part of Tool's BIOS prediction system called "Crystal Ball", when MSI release a future BIOSes for your board,
Tool can find them immediately. By that way the Tool no need to be updated to be actual in each moment
* Add new feature "True BIOS Version Ready"
- Updated Mode 1
- Updated Mode 2
- Updated Mode 3
Details:
Q: What "True BIOS Version Ready" means? Does the Tool show the wrong BIOS version until now?
A: Of course not, the Tool always show accurate info.
The same as CPU-Z/Everest of whatever other Tool.
However Tool also detect EC-FW versions for notebooks:
The "True BIOS Version Ready" Tool's feature is aimed to eliminate user's mass confusion about MSI BIOS versions.
And not only users are confused, but MSI's Live Update is confused too... which confuse users even more..
Few typical real examples of confusion:
"K9A2 CF wont flash to Bios v. 1.A !!!"
Quote from: Fingon on 25-October-09, 16:53:15
Hi MSI,
I have a problem. I have bought a new processor: AMD Phenom II x545. I looked on the support page of my MB (MSI K9A2 CF) and there the CPU is supported from the bios version 1.A. So I wanted to flash the Bios the the newest version (1.A). I used the MSI live update 4 program to flash it via windows mode. But everytime it boots it writes "CMOS checksum BAD", then I hit F1 to Bios and I see the version of my BIOS fell to the oldest version 1.1. Then I tried to flash it thru Flash disc (with boot files) and dos mod. The result is the same. I can flash my MB to version 1.8 but when I try the 1.A it wont flash it and my Bios fell to the oldest version (1.1). I realised that the exe files in version 1.1-1.8 are the same (afud412.exe) but the exe file in 1.A is different (afud4310.exe).
My questions are:
1) How to flash my MB to the version 1.A ?
2) Is version 1.A really needed for AMD Phenom II x545? I guess yes, because CPU was avaible in July 2009 and the bios 1.A went out in June 2009. I am able to flash it only to version 1.8 (december 2008).
Thank you for any help!!
EDIT: After reading this topic: https://forum-en.msi.com/index.php?topic=129204.0 I realised I have the VERSION 1 of this board (I purchased it right after the launch of the MB (November 2007). It means it doesnt support CPU over 95W, but my Phenpom II x545 has only 80W. I still cant update Bios to the 1.A version.
So my third question is:
3) Is the Bios update 1.A only for version 2 of this MB?
Thx for replies!
Quote from: Jack t.N. on 25-October-09, 17:16:16
A CMOS Checksum error is normal and expected after a BIOS Flash and/or a CMOS Clear. The fact that this message appears, shows, that there was actually something programmed to the chip.
If you haven't done that yet, please clear CMOS with the main A/C power cable removed from your PSU and load "Optimized Defaults" in BIOS Setup.
The BIOS Version should be shown on the POST Status Screen and there should be a date behind it. Please check the BIOS Date and write it down:
Are you absolutely and entirely sure that what you see is "1.1" and not "1.10"? Because v1.A0 is actually just the hexadecimal notation for v1."10" (one dot ten). The hexadecimal notation is only used in the BIOS File Ending. Once flashed, the BIOS will not identify itself in hexadecimal notation but in decimal code (which means you will never see "v1.A0" after the flash but "v1.10" instead.
Here is a piece of well-meant advice for now and the future: MSI Live Update should be avoided under all circumstances when it comes to BIOS Updates and/or information retrieval regarding your current BIOS Version. Why? Because this tool is stupid and one of there most risky applications for performing a BIOS Flash. Please uninstall it completely.
Why do I call it stupid? I call it stupid because it does not differentiate between hexadecimal notation and decimal notation. It will show you that "v1.A0" is available. The it will flash it, if you allow it to do so. Of course, a v1.A0 Version will always come out as "v1.10" (one dot ten). When you re-run MSI Live Update it will not recognize that v1.A0=v1.10 and tell you again that there is a newer version available (1.A0, which, again, is the same as v1.10, which was just properly flashed).
I believe that the update went just fine, that you are currently using v1.A0=v1.10 and that MSI Live Update is actually just creating a pseudo-problem which is currently confusing you. The pseudo-problem will immediately be out of the world, if you uninstall MSI Live Update and rely on the BIOS ID String as it appears on the POST Status Screen (this includes the date shown there).
If a BIOS Update should ever be necessary again, please make sure that you won't use MSI Live Update but >>Use the MSI HQ Forum USB flasher<< instead.
Quote from: Fingon on 25-October-09, 18:03:44
Thank you for the quick reply!!
Thats exactly what I have JUST found in this post by Svet: https://forum-en.msi.com/index.php?topic=127672.msg974800#msg974800
Yes it is 1.10 of course!! I didnt know that 1.10 = 1.A0 ! Thank you for the reply. Then the MSI live update 4 program is dump that he wanted from me another update of Bios.
So thank you! Problem is solved.
Edit: Yes, because of MSI live update I learned how to flash bios via flash disc. :-) But I was still confused by that 1.10 and of course by program saying me I should update again.. :-P
Quote from: Lostsoul777 on 14-August-09, 05:46:25
I had the same problem with 1.90 bios, so i updated to 1A, i just want to know why Bios Version says: v.1.10 instead v.1A?
Quote from: LinuxGuy on 29-December-09, 01:17:45
My computer does not have a floppy drive. How do I update the BIOS? (I tried the online utility 3 times. It always updates the BIOS "successfully" and when I restart my PC, I have to do either F1 to config or F2 to load setup defaults. So it looks like it's working, but the online update says that I have versions H.10 and version H.A0 is available (or maybe the other way around). So either the BIOS is getting updated, but the online tool is not recognizing this or it's not getting updated. Either way, I would like to manually flash it in DOS. Is it safe to burn the setup files to CD and boot from CD into DOS?
That's the same BIOS version... Just the "MSI Live Updater" is not very smart...
H.A=H.10=17.A=17.10 [A=10, H=17], the last "0" suffix in H.A0 means its official version.
Quote
I tried the online utility 3 times. It always updates the BIOS "successfully" and when I restart my PC, I have to do either F1 to config or F2 to load setup defaults.
So it looks like it's working, but the online update says that I have versions H.10 and version H.A0 is available (or maybe the other way around).
So ignore this MSI Live Updater's no sense, and stop flashing your BIOS. You already have the latest version installed.
The Tool now will detect and shows BIOS versions alias when the MSI BIOS version is known with more than one name.
So no more flashing and flashing and flashing to the same version because of MSI LiveUpdate suggest again BIOS update...
Also no more confusion:
"What's my BIOS version?" -> I flashed my BIOS to 1.A0 [A7520IMS.1A0], but BIOS says its 1.10
And MSI Live Update also says that i have 1.10 and 1.A0 is available and i should update it. I flashed it again, but its still 1.10?
What's going on?
Just run the MSIHQ USB Flash Tool and will show you all that you need to know
Examples[with real/accurate info]:
MSI Eclipse:
BIOS version 1.9:
BIOS version 1.10:[Tool now shows both BIOS versions alias]
Report stored respective in MSIHQ_INFO.TXT at user's desktop:
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in ба 30.12.2009 Ј. at 5:30:55,34
Mainboard: Eclipse SLI (MS-7520)
PCB Version: 1.0
BIOS Version: V1.9
BIOS Date: 09/22/2009
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in ба 30.12.2009 Ј. at 5:37:25,66
Mainboard: Eclipse SLI (MS-7520)
PCB Version: 1.0
BIOS Version: V1.A (aka Version: V1.10)
BIOS Date: 10/27/2009
More examples =>K9N6SGM-V / K9N6PGM-FI / K9N6PGM-F :
More examples =>945GCM5-F V2 (FSB 1333) :
Report stored respective in MSIHQ_INFO.TXT at user's desktop:
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in ба 30.12.2009 Ј. at 5:47:34,35
Mainboard: MS-7267
PCB Version: 4.0
BIOS Version: VH.9 (aka Version: V17.9)
BIOS Date: 11/20/2008
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in ба 30.12.2009 Ј. at 5:52:46,26
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: VH.A (aka Version: V17.10)
BIOS Date: 06/02/2009
More examples =>780GT-E63 [N/A at MSI web yet] :
For MSI Notebooks such decoding isn't need, examples:
* Add new feature "Triple BIOS flash Recovery Ready"
- Updated Mode 1
- Updated Mode 2
- Updated Mode 3
Details:
The feature include 3 auto prepared BIOS backups for followed purpose:
* Internal BIOS recovery:
- In a failure case Tool perform auto flash recovery [3 attempts, check for success after each and stop flashing if successful] before give control to BK_IO2, notice users about results and give control for manual attempts[if need]. [This a case if system isn't lockup/reboot, if bad flash occur]
- This mode also have own store up to 5 backups[+1, the last saved copy is always backup.bin, if there was older one they become backup1.bin .. till 5]
* BIOS backup stored as AMIBOOT.ROM [AMI BIOS only] [Auto clean up older if there is any, before take a new backup to avoid recovery confusion]
* BIOS backup detected and stored for M-Flash style boot/recovery [AMI BIOS only] [Auto clean up older if there is any, before take a new backup to avoid recovery confusion]
Performing test simulations with random generated BIOS versions[including betas] for M-Flash boot/recovery style, some examples:
Copy/paste Tool log file:
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:00:53,46
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: VD.XB2 (aka Version: V13.33B2)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.DX2
Where:
* V13.33B2 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* VD.XB2 ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.DX2 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:12:23,95
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: VK.VB7 (aka Version: V20.31B7)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.KV7
Where:
* V20.31B7 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* VK.VB7 ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.KV7 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:18:34,46
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: V3.9
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.390
Where:
* V3.9 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* MSIHQ Tool "True BIOS Ready" detection feature isn't need here, since this BIOS version can be known only with one name.
* A7267IMS.390 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:22:24,04
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: V8.1B9
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.819
Where:
* V8.1B9==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* MSIHQ Tool "True BIOS Ready" detection feature isn't need here, since this BIOS version can be known only with one name.
* A7267IMS.819 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:25:38,51
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: V4.E (aka Version: V4.14)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.4E0
Where:
* V4.14 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* V4.E ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.4E0 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:28:16,62
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: V1.BB1 (aka Version: V1.11B1)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.1B1
Where:
* V1.11B1 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* V1.BB1 ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.1B1 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:31:57,78
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: VI.FB5 (aka Version: V18.15B5)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.IF5
Where:
* V18.15B5 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* VI.FB5 ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.IF5 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:36:02,40
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: V7.O (aka Version: V7.24)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.7O0
Where:
* V7.24 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* V7.O ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.7O0 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:39:11,84
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: VC.8B6 (aka Version: V12.8B6)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.C86
Where:
* V12.8B6 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* VC.8B6 ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.C86 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:49:38,46
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: VG.PB6 (aka Version: V16.25B6)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.GP6
Where:
* V16.25B6 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* VG.PB6 ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.GP6 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:53:17,26
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: VU.H (aka Version: V30.17)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.UH0
Where:
* V30.17 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* VU.H ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.UH0 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]

Vendor Payment Advice - idoc PEXR2002

Dear guru,
My customer would like to receive a payment advice from the bank regarding the vendor payments done.
It means that after processing the F110 and sent the payments to the bank, we will receive an acknowledgement idoc from the bank in order to inform us that all payments have been correctly processed.
I have seen that the idoc PEXR2002 can be used as "payment advice" with message type REMADV for instance. But all the cases that i have seen concerned customer payment advices sent directly by them.
Is anyone know if it is possible to use this idoc in order to retrieve the payment information for vendor and not customer?
If yes, where can we retrieve those information in SAP? Besides the table AVIK/AVIP, can we check the payment advice integration somewhere else (reports, financial document)? because in our case we just want to retrieve the confirmation of payments but there wont be clearing between payment/vendor invoice because it will have been already done at F110 processing.
I hope this is clear enough.
Thanks a lot for you help
Guillaume

Hi Afzal,
For sending Payment advice by E-Mail, "You need to copy SAMPLE_PROCESS_00002040 and adjust it to write code as per your requirement. This BTE runs for each payment advice note to be sent and in the module, it is mentioned 1=print, 2 = Fax and I=mail, so you can set your priority, that if an E-Mail address is maintained in the vendor master, send mail or if no E-mail address is maintained send Fax, and if both are not possible shoot a Print.
From Configuration side, you need to maintain the Z copy of SAMPLE_PROCESS_00002040 in FIBF transaction under the Process module of a customer without country or application indicator.
SAP Note 836169 - Consulting: Payment advice notes by email or fax.
Regards,
SAPFICO

I am unable to synch music from selected playlists in my iTunes library onto my new iPod Classic, despite meticulously following the User Guide.

I just purchased an iPod Classic, and after making sure I had the latest ver. of iTunes on my Intel MacMini, printed out the User Guide and carefully began learning how to operate the iPod. My first step was to ensure I had manual control (vs. auto synch) because I want only selected songs and playlists on the iPod, not my whole iTunes Library.
On pg. 24 of the Guide is the topic "Synching music from selected playlists onto iPod Classic." Just what I wanted. OK, I selected iPod "in the source list" (aside: Shouldn't it be "in the device list?" I dispair of imprecision). This brought up the iPod Summary page, showing I had selected Open iTunes when connected and Manually manage music and videos. Next I clicked on the Music tab.
This presented me with Synch Music next to an empty check box. Below it, and entirely grayed out was:
Entire music library (showing a checked box)
Selected Playlists, artists, albums and genres (next to an unchecked box).
There's also a third grayed out item: Include music videos that is checked.
When I selected Synch Music, I got the message: "Are you sure you want to removed existing mlusic, movies and TV shows from the iPod and synch with this iTunes LIbrary? I selected Cancel because:
1. The grayed option Entire Music Library is checked, not mly preferred option of Selected playlists, artists, albums and genres. .
2. I can't find anywhere in the User Guide how to "Select the Playlists" I want to synch to my iPod. At present all I have in iTunes is my list of playlists in the left hand side bar.
OK, my first thought was the checked box in the iPod's Summary window: Manually manage music and videos. So I went there and unchecked it, which immediately brought up an alert to the effect "Are you sure you want to automatically synch your entire iTunes library, etc. etc...? I quickly cancelled. Thus, I seem to be in a Catch-22 situation.
So the questions are:
How do I resolve the Synch Music issue so I am assured only selected playlists will be sent to my iPod?
How do I create a list of playlists in my iTunes library to be transferred to my iPod?
How do I manually move a playlist in my iTunes library to my iPod's lists of playlists?
Any help much appreciated. Thanks to all.
John in the Pacific Northwest

For the immediately problem, you can shut down the computer and disconnect the iPod.
There may be a process (program) running on your computer in the background that continuously monitors mounted volumes for things like maintenance, data corruption, and malware. The iPod's storage is a mounted volume. If you know of any such program, such as an "anti-virus" utility, and it has settings that allow you to exclude certain volumes, you can set it to ignore the iPod "disk" when connected.
Also, if you are using automatic syncing (not the manual method) to load the iPod, and you have Enable disk use turned ON, turn it OFF. With Enable disk use turned OFF, iTunes only mounts the iPods disk when syncing, then immediately unmounts the disk. Thus, other processes you have running on your PC (not iTunes) will have less of a chance to make the disk "in use" and cause this problem. You won't even have to eject the iPod before disconnecting.

Can't access User Guide after Windows 7

I did a clean install of Win 7 on my HDX 18 and it went very smoothly. Even all my MediaSmart apps and buttons work (except eject which I see doesn't work for many).
One minor detail is that the User Guide won't open. I have HP Support Assistant and on the "Learn" tab there are various items to click to learn more about your computer. All work except the User Guides. I get the following error message...."This program is not installed."
However, I did install the User Guides. It is even listed in Control Panel, Uninstall Program as "HP User Guides 0116." Anyone know why the HP Support Assistant can't find them? I also don't see them installed anywhere as there is no start menu item to click to see them.
Thanks.

My computer came with win 7 home premium x-64 installed.
I installed a 2nd hard drive and installed windows 7 ultimate x-64 on it - now I can boot either one.
I downloaded and installed the latest HP Support Assistant under win7 ultimate, but got the "this is not installed' message when trying to access user's guides from support assistant, and indeed, the user's guide are not in C:\Program Files (x86)\Hewlett-Packard\Documentation, so I copied x:\Program Files (x86)\Hewlett-Packard\Documentation (where x: is my original hard drive) to C:\Program Files (x86)\Hewlett-Packard\Documentation, and now it works fine from support assistant.
Also I can double-click on C:\Program Files (x86)\Hewlett-Packard\Documentation\HpDocViewer.exe in explorer, and the user's guide comes up.
Sorry, I don't know why it doesn't work for both of you, but try just running HpDocViewer.exe in the Documentation folder.

Error in IDOC processing - Message no. VU 014

Hi All,
I got error while processing IDOC manually as:
" Incompletion: Vendor : Account number of vendor or creditor (VBPA -LIFNR ), error group: 08"
Details of Error message are as below:
Message no. VU 014
Diagnosis: The incompletion check reveals, for analysis purposes, any incomplete documents.
The message contains:
1. A description of the incomplete document
2. A technical entry, telling you which table field has been checked
3. A the error groups in the transaction from Customizing for Incompletion Log.
Procedure
One solution is to deliver the affected document in the screen (Create delivery with reference to order), and to edit and save the delivery following the menu path: Edit -> Incompletion.
In certain circumstances, you can change Customizing so that
the checked field is no longer assigned to the error group
or
assign another error group to the document type /item category
or
permit the delivery as a subsequent function.
I am confused about what could be the root cause of the error and how to solve it.
The Important thing is, when IDoc is run in Automatically(batch run), then it is successful with no any error but it gives this error when i run it manually.
Pl. guide me to solve this problem.
Thanks,
Jai.

Hi Bernd,
Thank you for your mail.
The Note 991410 is related to the IDoc status 53. I stucked with the IDoc status 51.
IDoc error message is in status 51. But still I am looking all other alternative inculding one you suggested.
Thanks you very much.
Jai.

Clean install from a Lenovo installa. dvd: UEFI vs Legacy + Thinkpad setup acc. to Lenovo user Guide

Machine: T520 bought Feb. 2012
O.S. W~7 Pro 64-bit
I want to wipe the harddrive, buy a Lenovo W~7 PRO installation DVD, and do a completely clean installation.
Lenovo User Guide (.pdf) Ch. 8, Adv'd Config, Installing Windows 7, p. 295 (212 of 298) says:
Start Thinkpad setup, then choose UEFI versus Legacy, then insert the installation DVD.
This obviously does not apply when the harddrive has already been wiped (necessary to 100% eliminate all traces of irreversible damage caused by a virus, including the re-installation partition (Q-drive).
When an intallation DVD is purchased from Lenovo, is not the first step to insert the DVD ?!! Then presumably there is an installation wizard resulting in a restored O.S. ?!!
If not, please tell me what surprises are in store, and where I can find a reliable written resource to consult !!!
Thank-you.
Solved!
Go to Solution.

You're over-thinking this and making it harder than it needs to be. The manual isn't helping...
The BIOS is stored in non-volatile memory on the motherboard. One would probably call it firmware, not software. It is there regardless of what's on the HDD - or whether there's even an HDD installed.
Turn your machine off. Turn it on again. When you see the logo screen, hit F1 - multiple times if necessary. That gets you into the motherboard's BIOS configuration utility - what the manual is calling "Setup".
Here's a snip below from the T520 BIOS configuration utility (actually from the on-line BIOS simulator). In the StartUp tab you can see where UEFI/Legacy can be selected. You can configure UEFI boot there. Or "both". Or - probably - just select Setup Defaults, save, and exit.
Z.
The large print: please read the Community Participation Rules before posting. Include as much information as possible: model, machine type, operating system, and a descriptive subject line. Do not include personal information: serial number, telephone number, email address, etc. The fine print: I do not work for, nor do I speak for Lenovo. Unsolicited private messages will be ignored. ... GeezBlog
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество

User Guide missing from downloads

I've noticed that the User Guides are now missing from the downloads for various models. Is there a reason for this ? Although you can still retrieve them via Google, I was just easy finding them on the download page.
Owner & Operator of the following:
● Lenovo Ideapad Z570 w/ Win 7 & Win 8.1 Dual Boot ● Lenovo Yoga 3 Pro w/ Windows 8.1 ● Toshiba A75-S206 w/ Win 7
● IBM Thinkpad T-23 w/ Win XP ● IBM Thinkpad T-22 w/ Win XP • As well as multiple desktops dual/triple booting XP, Vista and Win 7.
★ Find a post helpful? Thank that member by clicking on the ☆Star☆ to the left awarding them a Kudo.
★ Posting a problem and a reply is helpful and it answers your question, please mark it as an "Accepted Solution"
★ I'm not a Lenovo employee, just a volunteer geek who likes to help folks. Enjoy your time here, pay it forward by helping others !
★ Sorry, I don't answer questions via Private Messages. Posting in the appropriate forum is the best way to get assistance.

Majestic,
I've routed this to the eSupport team. Should hear from them soon
Thanks!
WW Social Media
T61, T410, x240, Z500, Flex 14
Important Note: If you need help, post your question in the forum, and include your system type, model number and OS. Do not post your serial number.
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"!
Follow @LenovoForums on Twitter!
How to send a private message? --> Check out this article.
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество

Idoc PEXR2002 is not getting tiggered frm T-Code F110

Hi All,
I need to trigger the Idoc PEXR2002, from the T-Code F110. The payment process is successfull, but the Idoc is not getting triggered. I am not able to find the exact reason for that.
We have a tab with name printout/data medium and it has got the following programs in it 1. RFFOAVIS 2. RFFOEDI1 3. RFFOUS_C. Is there any thing I need to do with these??
Please help me..
Thanks
Suma.

Hi suma,
Now i have requirement to generate payment file
whan we execute F110 using enhancement IDOC(EDI) . I want to know ,by which method i can trigger
IDOC ( by message control ,work flow or standard program) .if it is message control what is process
code for this.
I think u have worked on this .if u have information abt this plz forward me .
Thanks & regards,
Balu.

IDOC status "Message scheduled on outbound side"

Hi,
I am working on scenario file->XI->SAP R/3(Using IDOC). I am getting outbound status of IDOC as "Message Scheduled on Outbound side". When I go and see SM58 for user WF-BATCH there exists a entry with status Transcation Recorded". In SM58 if I manually click Execute LUW then only I am getting an IDOC posted in my R/3 box, but this should happen automatically.
Can any one tell me what should I do so that it gets executed automatically?
Thanks In Advance.
Yaseen Mahammad.

Most of the time it is because of the Queues and Logical system. I,e If there is no proper logical systems are created/maintained then it will give problem.
And it also depends on the rfc Dialog users.
Just check this thread-
Problem with IDOCS
Also check in the IDX1 entry...
Thanks,
Moorthy

Inbound Processing of iDoc Status Message

Silly me - I thought this would be simple ...
I am currently changing our bank interface from a customized ABAP solution to use more standard SAP utilities (particularly iDocs). I have the configuration set up to use the PAYEXT message type sending PEXR2002 iDocs to a file port. Our bank is receiving these documents and is returning an iDoc status message containing the status of each payment iDoc that they received from us.
My problem is that I can't figure out how to get these status iDocs to update the status of the corresponding PEXR2002 iDoc.
I am trying to execute an RFC interface to apply these status messages to my system using the following OS command:
D:\usr\sap\VPR\SYS\exe\uc\NTAMD64\startrfc.exe -3 -d RT2 -u xxxxxx -p xxxxxx -c 220 -h SPR32K36 -s 00 -F EDI_STATUS_INCOMING -E PORT=ZFI_INT003
The error message that I receive when this is run is:
RFC Call/Exception: SYSTEM_FAILURE
Group             Error Group 104
Key                RFC_ERROR_SYSTEM_FAILURE
Message        Status record 1 is invalid (TABNAM: 'EDI_DC40')
The port (ZFI_INT003) is the file port that is configured for the outbound file. in WE20, this port has the "Status File" tab set to use the logical file name where the status file is being stored on the server. the startrfc command is connecting to the SAP system and opening the status file. I'm not sure where I'm going wrong here.
Can someone please help get me pointed in the right direction? I've obviously missed something here.
Thanks,
Glen

Hi,
call function modules:
EDI_DOCUMENT_OPEN_FOR_PROCESS
   EDI_DOCUMENT_STATUS_SET
   EDI_DOCUMENT_CLOSE_PROCESS
kind regards,
HP

IDOC PEXR2002 Address Fields

Hi,
I notice in IDOC PEXR2002, there are only 2 address fields - Street and Street 1. How can I interface the IDOC to my bank if Street 2 and Street 3 from Vendor Master are also needed?
Any workarounds?
Thanks.
Regards.

Do you mean I can add more fields to the standard IDOC?
I understand there are some user exits for this IDOC.

RFC error "No authorization to send IDOCs with message type ..."

Hi all,
I have now tried just about everything I could think of, applied all the notes mentioned on this forum but still no luck. Can anyone please help ...
I have got a file to idoc scenario, the status in the sxmb_moni is successful, but the outbound processing logs an error. When I go to transaction SM58 I get an error for the user XIAFUSER with the message "No authorization to send IDOCs with message type WPUUMS".
I have tried giving this user SA_ALL access and still got the same error thus concluding that this is not an authorisation error.
Any suggestions?
Regards,
Liesel

Hi Liesel,
The RFC destination that you have put in IDoc communication channel must be present in your SAP XI system, transaction SM59 also.
Please check if the user id/Password that you have given has all the authorization.
Also check the User ID and passwrord in SM59 in R3 and see if a Remote Login is possible.
There is also some configuration by which the clients are allowed / blocked from receiving Idocs from XI. Basis guys can do it for you. Please approach your basis consultant. Hopefully that helps..
Regards,
Abhy Thomas

Error : No authorization to send IDocs with message type MATMAS

Hi All,
My scenario is FILE-XI-IDOC.
I am getting chequered flag in SXMB_MONI,but in that under outbound status I am getting red flag.
When I check in SM58 I am getting message as "No authorization to send IDocs with message type MATMAS".
Do I need to give any authorizations on XI side or on R/3 side?
If so, what is the authorization required?
I could not find the note :837595.

<i>You use the IDoc Adapter in the Exchange Infrastructure and you try to use the IDocs to receive or send data. For these IDocs, an attempt is made to load the IDoc metadata from an R/3 reference system with an SAP NetWeaver Release lower than 6.20.
This occurs either at runtime, whereby the relevant messages run into 'System error' status, or when you use transaction IDX2 during manual loading of the metadata. In this case, the reference ystem is called by RFC and the logon user of the RFC destination does not have the necessary authorizations for determining the metadata.
Solution
In transaction PFCG, extend the role of the logon user by adding the following authorizations:
Authorization object S_RFC
      Field name RFC_TYPE value FUGR
      Field name RFC_NAME value EDIMEXT, SDTX
      Field name ACTVT    value 16
Authorization object S_IDOCDEFT
      Field name ACTVT value 03
      Field name EDI_CIM value ' '
      Field name EDI_DOC value TXTRAW01
      Field name EDI_TCD value WE30
Authorization object S_CTS_ADMI
      Field name CTS_ADMFCT value TABL
Authorization object S_TABU_DIS
      Field name ACTVT      value 03
      Field name DICBERCLS value</i>
from the note mentioned above.
Regards
Bhavesh

Workflow Ends in Error " No auth to send IDocs with message type ORDRSP"

Hello All,
I have created an RFC user with limited Authoprizations including WE* tciodes and a few ME* transactons for an ALE Set up. I want to make sure i would not be giving more authorizations (extensive) to this RFC user and assign Just required authorizations. So i started testing testing and the inbound IDOC ended in error with a message " No auth to send IDocs with message type ORDRSP" Message no. SR053. Is there any way to find out what is the missing authorization object for the User. Any inputs would be really apprecaited.
Br,
Sri

Hi !
Becaus alle this happens in beckgound, things are a bit difficult but solvable....
What you should do is a "Authority trace" ... as follows....:
- Go to the ST01
- Mark "Authorisation Check"
- Swich the trace on for your Workflow user
- Execute the Workflow until the error uccurs
- Go back to the ST01
- Press the "Analyze" button and see what error occurs
Dont forget to swicht the trace off... otherwise the tracefiles become realle BIG !
Regards
rainer
Some Reward poins would be nice if that helped....

Idoc PEXR2002 Message User Guide

Similar Messages

Maybe you are looking for