Root device not read-write warning

There's a new warning message (https://projects.archlinux.org/mkinitcp … a191b3233a) that goes like this:
WARNING:
The root device is not configured read-write! It may be
fscked again later!
I was told to configure grub correctly but whatever I do I always have to manually modify /boot/grub/grub.cfg
and remove " ro " even if I explicitly add " rw " in /etc/default/grub. How can I make grub-mkconfig not put " ro "
in /boot/grub/grub.cfg? Is this documented somewhere?
I considered using syslinux instead but couldn't figure out how I can install it somewhere else than MBR.
Last edited by cm (2013-07-24 14:42:52)

falconindy wrote:Perhaps you should post your /etc/default/grub ...
/etc/default/grub
GRUB_DEFAULT=0
GRUB_TIMEOUT=1
GRUB_DISTRIBUTOR="Arch"
GRUB_CMDLINE_LINUX_DEFAULT="quiet rw"
GRUB_CMDLINE_LINUX=""
# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
# Uncomment to enable Hidden Menu, and optionally hide the timeout count
#GRUB_HIDDEN_TIMEOUT=5
#GRUB_HIDDEN_TIMEOUT_QUIET=true
# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console
# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE=auto
# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep
# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true
# Uncomment and set to the desired menu colors. Used by normal and wallpaper
# modes only. Entries specified as foreground/background.
#GRUB_COLOR_NORMAL="light-blue/black"
#GRUB_COLOR_HIGHLIGHT="light-cyan/blue"
# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/path/to/wallpaper"
#GRUB_THEME="/path/to/gfxtheme"
# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"
#GRUB_SAVEDEFAULT="true"
falconindy wrote:Yes, using the 'systemd' hook is an option. An option and not a requirement. Just fix your kernel commandline to specify 'rw' instead of 'ro' (or nothing) so that your root device is mounted rw after fsck'ing.
How do I specify 'rw' instead of 'ro' the correct way with grub?
Last edited by cm (2013-07-24 14:44:25)

Similar Messages

  • After reinstalling MAC OS 10.6.8, config the permissions to read/write/no access, my MacMini [mid 2010] refuses to reboot. I tried to reboot in safe mode with fsck, but after the steps to be taken, it says fscs not done, root device is read only

    After reinstalling MAC OS 10.6.8, I config the permissions to read/write/no access, my MacMini [mid 2010] refuses to reboot. I tried to reboot in safe mode with Command+S and fsck, but after the steps to be taken, it says fscs not done, root device is read only. I also tried to bypass the Mac firmware password by taking one Ram card out and reboot the macmini while holding COMMAND+OPTION+P+R. But no luck. The macmini is not able to see the mac OSX installation CD.
    Please help ??

    f.fromleiden wrote:
    After reinstalling MAC OS 10.6.8, I config the permissions to read/write/no access, my MacMini [mid 2010] refuses to reboot.
    How and where did you change which permissions? And what was the goal?
    Do you have a complete backup of your system? and more importantly data files?
    What happened that prompted the need to reinstall the 10.6.8 update?
    The immediate road forward would be to boot from the optical drive and revert the changes you made.
    What happens when you boot with the install cd and hold down C or hold down the option key?
    [Off topic: I've been to Leiden a few times ]

  • Why my device not read pdf-files in mail messages?

    Qq
    why my Nokia device not read pdf-file on mail message?

    What is the operating system on that device?
    Do you have Adobe Reader installed?
    What exactly means "not read"?

  • How to: Create a Program with the rs232 Device -Magcard Reader Writer

    Hi Guys!. 
    Im New in using VB.net 2010 express 
    and it is my first time to do a project with a device needed to incorporate with it.
    I have a device Magnetic Card Reader writer and a i want to create a connection and UI 
    that interacts with the device alone without using the default application and process.start command.
    the main problem i want to be solve is to perform the connection and commands on a single form by allowing the user to read and write the data on a single form. 
    what i want to do is to create a main form that executes the commands needed to activate the event or allows the user to use the device w/o using the software. with the use of text box and button, while the read executes automatically if the card is swipe
    to it end fill out the focus textbox given.
    i have here a document that discuss commands for the device and i think it is needed to successfully connect all the process from device to the system
    can you help me to do this project? tnx.. :)

    Hi,
    Welcome to MSDN.
    I am afraid that this is not the proper forum for this issue, since each  Magnetic Card Reader writer has its API for developers.
    You could consider getting supports by connecting with the publisher of that Magnetic Card Reader writer which should have the sample about using its API.
    In addition, I did a research, you could refer to
    Build a .NET Class for Serial Device Communications with P/Invoke to get how to communicate with that serial device.
    Thanks for your understanding.
    Regards.
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • "Root device is read only"-?

    Hi!
    I want to test my RAM using Memtest and start the Mac in Single user mode. But at the bottom of a long text, it says
    "Singleuser boot -- fsck not done
    Root device is mounted read-only"
    What does this mean, and how can I change it?
    OS 10.6.4
    Kind regards - Hening.

    baltwo,
    AFAIK, there's no benefit running the test in single-user mode. Just download Rember and run it.
    Well the text displayed in the shell during the execution says that multi-user mode may be less reliable and complete. In my case, only 5 of 6 GB of RAM were tested.
    So I tried to run memtest in Single User mode. The prompt looks like this:
    :/root #
    and I type the path to the memtest folder which in turn contains the memtest tool; dates is the name of the volume, hening is my Home folder, bin is a folder in which I store bins:
    cd volumes/dates/hening/bin/memtest ENTER
    and get
    "no such file or directory"
    What am I typing wrong?
    I wanted to try "~" for home folder, but can not find the tilde when in the command line interface. When I am in "normal mode", choose the US keyboard layout and open the Keyboard Viewer, it tells me that the tilde maps to "shift-<"-" on mine, and that worked. The keyboard I am using is a wireless keyboard with german Windows layout.
    By the way, when I want to start in Single User Mode, I have to use the (wired) Apple keyboard; the cmd-s combination does not work in the intended way on my wireless one. However, once I am in the shell, the Apple keyboard strangely does NOT work any more, whereas the wireless one does.
    Kind regards - Hening.
    Message was edited by: hening

  • [Solved] - Root device not found - Unable to boot!

    Before posting links to other threads or to the pacman/mkinitcpio wiki page please go through the following.
    I know that many others are facing a similar problem, but I am posting this after spending 8+ hours (in 2 days) trying to get my system to boot.
    And worst of all I don't have a working CDROM so I have to boot via an iso on a pendrive which is very frustating.
    The exact message I get after the GRUB menu is:
    ERROR: resume: hibernation device '/dev/sda3' not found
    ERROR: Unable to find root device '/dev/disk/by-uuid/...'
    You are being dropped to a recovery shell.
    Type exit to try and continue booting
    Now I have already tried the following, by chrooting into my system:
    1. As per the pacman wiki page, boot via live arch, chroot and run full upgrade. Then reinstall udev followed by mkinitcpio and then remake the image.
    2. Downgrading to linux-3.3.4-2, udev-182-2x86-64 and mkinitcpio-0.8.8-1
    3. Rearranging hooks in mkinitcpio.conf (usbinput before udev), and adding ext4 to MODULES array. Done this in both downgraded version and new kernel version (3.3.8-1)
    After trying various permutations and combinations, I have failed and haven't been able to get past the first 8 lines after the grub menu.
    An important point to note:
    I had used the --force switch for 1 more package other than filesystem while updating which I don't remember now. I had to use it because some packages had gotten corrupted while downloading and I had to upgrade in parts. Also at no point during any of these trials did I get an error while rebuilding the initrd image.
    If I remove the resume hook in /etc/mkinitcpio.conf then the first line "ERROR: ... " changes  saying that "no hibernation device specified".
    Please suggest anything if you can!
    Last edited by theta (2012-06-15 15:44:15)

    ewaller wrote:
    Do you know the partition that is supposed to be your root partition?
    Grub cannot find it by its UUID.   Reboot, at the grub menu, highlight the kernel you want to boot, and press 'e'.  You are dropped into a simple editor which will allow you to change the boot command.  Replace references to /dev/disk/by-uuid/... with /dev/sdan, when n is the root partition number.
    One other possibility.  Does your system have multiple drives?  Any chance the BIOS could be swapping them ?  (On second thought, that would not break UUID, But... it is something to be aware of using the technique I proposed)
    If you do not know the partition arrangement, use that limited recover shell you mentioned to go look around and determine it.
    Hmm, Thanks for this advice but I can't help saying that I'm not a noob .
    Somehow the problem resolved itself with the new kernel update which came about half an hour ago (3.4.2-2). Suppose it will remain a mystery now!

  • [SOLVED]kexec into arch fails : root device not found

    Hello,
    I have a fresh arch install with only base, base-devel and openssh.
    I boot on penbuntu, at this point I can see my devices in /dev.
    Then I mount my root arch partition on /mnt/rootfs and do :
    kexec --load /mnt/rootfs/boot/vmlinuz-linux --initrd=/mnt/rootfs/boot/initramfs-linux.img --command-line="root=/dev/sda3 ro vesa video=vesafb"
    which returns :
    setup_linux_vesafb: 1280x720x32 @ 10028000 +708000
    I then do kexec -e, It seems to start loading the kernel since the screen is cleared and each time it does
    [0.845500] i8042: No controller found
    :: running early hook [udev]
    :: running hook [udev]
    :: Triggering uevents...
    Waiting 10 seconds for device /dev/sda3 ...
    ERROR: device '/dev/sda3' not found. Skipping fsck.
    ERROR: Unable to find root device '/dev/sda3' /
    You are being dropped to a recovery shell
    Type 'exit' to try and continue booting
    sh: can't access tty: job control turned off
    [rootfs /]#
    I tried everything as root in the kexec --command-line, root=LABEL, root=UUID but it always do exactly the same thing, waits for 10s for device and then ERROR and drops to the recovery shell.
    Any idea of what's going on ? Why can't it see devices ?
    EDIT : If that can help, the kernel from which I am kexecing is 2.6.24.3 and If I try to just chroot I notice :
    mount -t proc proc proc/
    mount -t sysfs sys sys/
    Works but when I :
    mount -o bind /dev dev/
    It returns :
    mount: mounting /dev on dev/ failed: Invalid argument
    So somehow I think when the kernel loads it has trouble passing the /dev along and therefore sees no devices. But I still can't figure out what to do.
    Thanks in advance
    Last edited by Nolhian (2012-07-28 17:47:30)

    I can't because I'm booting on penbuntu and not arch linux. Anyways the command used in the wiki is similar to the one I'm using.

  • Airport express: iMac read/write to pc, pc can see iMac but not read/write

    airport express: my iMac can read/write files to my Windows 8 pc, not reverse. My PC can connect to my iMac (it shows on the PC as a network device) but cannot see any files or folders. Airport docs suggest that my Documents folder should be visible. Tried enabling access everywhere I can think on iMac such as SMB. Any help?

    Hi everyone
    I've managed to work out how to share my desktop and the external drive attached to it via wireless so my Macbook Pro can see, open, and edit and save photo files via Photoshop Elements.
    I can also then view and edit them through the Windows PC - though they say some properties are missing this I can live with.
    Therefore no re-formatting needed, and no downloads either.
    Many thanks
    Regards

  • Root device not created on boot.

    When booting i get the following error;
    Error: unable to create/detect root device.
    I am then dropped to a shell.
    This is just after the hook are run / during hook running. Only three of which are run, udev, keymap and filesystem. Others, including sata, are in the initrd file but are not run.
    The following is the grub entry for arch.
    title Arach Linux x86
    root (hd0,4)
    kernel /vmlinuz26 root=/dev/sda6 vga=791 noapic
    initrd /kernel26.img
    Any help would be appreciated,
    Christopher

    Sounds like the kernel image was not genereated correctly.
    Try booting the fallback kernel :
    title Arch x86 fallback
    root (hd0,4)
    kernel /vmlinuz26 root=/dev/sda6 vga=791 noapic
    initrd /kernel26-fallback.img
    check /etc/mkinitcpio.conf and regenerate the kernel image with mkinitcpio -g /boot/kernel26.img .

  • CD/DVD-drive does not read/write properly

    I can not write any dvds or cds because every time a message pops up with an error.
    I tried different burning programs with different cd manufacturers and it still does not seem to be a problem on other computers having the same program and using same cds or dvds.
    Another thing is that it can not read dvds all the time; same dvd can work once but not again and whenever i try to open a normal cd-r it says blank disc even when they work perfectly on other computers?
    can anyone plz help

    hey ..ok im on a toshiba laptop SA50-543 usind windows XP home edition..the dvd/cd thing is built in and is a DVD rewritabl CD rewritable multiple recorder.
    as for the programs i used for burning..i tried nero,sonic record now and the one im on now is roxio easy media creator
    as for the error msg it says:
    there was a problem writing to the disc.you can try again by clicking the retry button.you will need another blank disc ready.
    further info:
    Recording error
    Recording errors can occur when a disc contains dirt, fingerprints, or scratches.
    If you are getting recording errors:
    Try using a new disc.
    Try using a different manufacturer??s disc.
    Ensure the disc is clean before recording:
    Remove all fingerprints, dirt, and dust from the shiny side of your disc using a nonabrasive cloth with a mild, nonabrasive soap solution.
    Wipe the disc from the center to the edge.
    Dry the disc completely.
    tried doing all of that and still not recording..and anyway if it was aproblem with the cds why would they work fine on other laptops?
    i dont know which other info you need so let me know if theres anything else
    Oh yeah, theres an advanced explanation for the recording error but its all in numbers do you need to know that?
    thx

  • [Solved] kernel 2.6.27 - Root device not found (2.6.28 too)

    since the last kernel update, my ArchLinux won't boot anymore, as it seems to be unable to find the root partition "/dev/sda5". The exact output is:
    :: Loading root filesystem module...
    Attempting to create root device '/dev/sda5'
    ERROR: Failed to parse block device name for '/dev/sda5'
    unknown
    ERROR: root fs cannot be detected. Try using the rootfstype= kernel parameter.
    Waiting for devices to settle...done.
    Root device '/dev/sda5' doesn't exist, attempting to create it
    ERROR: Failed to parse block device name for '/dev/sda5'
    ERROR: Unable to create/detect root device '/dev/sda5'
    Dropping to a recovery shell... type 'exit' to reboot
    NOTE: klibc contains no 'ls' binary, use 'echo *' instead
    If the device '/dev/sda5' gets created while you are here,
    try adding 'rootdelay=8' or higher to the kernel command-line
    ramfs$
    What I have tried:
    1.- I have booted with an old Ubuntu LiveCD, and /dev/sda5 seems to be working and healthy, as it mounted flawlessly while in Ubuntu.
    2.- I have also found that not even /dev/sda is created from the fallback recovery shell so, obviously, there is no root device to create.
    3.- None of the suggested kernel command-line parameters worked: 'rootfstype=ext3' and/or 'rootdelay=8'(I mean, using them separately or both in the same kernel GRUB line) didn't give any positive result, or any behavior change.
    And now, two questions:
    1.- How can I fix this?
    2.- If it's not possible, how can I downgrade the kernel from a LiveCD? I suppose this is possible by booting an ArchLinux LiveCD, chrooting my '/dev/sda5' finding a 2.26.X kernel pacman package and installing, but I'm almost iliterate in kernel issues, and some help would be nice.
    Thank you all in advance!
    EDIT: Oh, I have also waited for some time to see if the hard disk gets ready after the failed booting proccess but it seems it doesn't, so 'rootdelay=8' wouldn't help anyway, just to give some more details about the problem.
    Last edited by 4s|m3tr|ko0 (2009-01-21 10:14:32)

    4s|m3tr|ko0 wrote:
    ballon wrote:It seems like my problems can be the same, however I haven't managed to solve it myself so if you can be more detailed that would be nice.
    Of course I can, it's quite easy.
    First of all, you have to boot from an Archlinux install CD, to have an usable environment. Once you have booted, I will assume a couple of things to make the examples, which are:
    "/dev/sda2" is the root partition where the system is currently installed but not booting.
    "/dev/sda1" is the boot partition (not needed if you don't have a separated boot partition, obviously).
    "/mnt/myarch" is the directory where sda1 will be mounted on the live session.
    The kernel version on sda2 is "2.6.27-ARCH", you can find which kernel versions are installed on sda2 by checking the directory names under "/lib/modules/"
    Next you have to mount your root partition on any directory and mount the "boot" partition if you have one too:
    mkdir /mnt/myarch #Creates the mount directory on the live session, you can use /mnt/ so this command is not neccesary
    mount -t auto /dev/sda2 /mnt/myarch #Mount the root partition on the live session
    mount -t auto /dev/sda1 /mnt/myarch/boot #Mount the boot partition, if you have to
    Now, you'll have to bind three system directories to their true locations on the root partition:
    mount -t proc proc /mnt/myarch/proc
    mount -t sysfs sys /mnt/myarch/sys
    mount -o bind /dev /mnt/myarch/dev
    Next step is to use the command "chroot <target> <consolebin>" to "move" the system root to the <target> directory, using the <consolebin> command interpreter:
    chroot /mnt/myarch/ /bin/bash
    Now, you will be using your system just like if you had actually booted from your hard disk, but running the kernel from the liveCD, so the only remaining step is to generate the initcpio image.
    In the example for this step, I will run the mkinitcpio twice, the first one to check that it's correctly generated, and the second to install it, using the parameter "-g". Another thing to keep in mind is that even before chrooting, the liveCD kernel is still running, so you will have tu use the "-k <kernelversion>" parameter to manually specify the kernel to use. Otherwise, mkinitcpio won't be able to find the correct modules to use:
    mkinitcpio -k 2.6.27-ARCH #This will simulate the generation, if it runs fine, run the next command
    mkinitcpio -g /boot/kernel26.img -k 2.6.27-ARCH #This will actually generate the image
    And that's all, this should regenerate a default image. More info about mkinitcpio: http://wiki.archlinux.org/index.php/Mkinitcpio
    Hope this heps
    PS: Sweden, nice country .
    I follow this guide and I saved my Arch installation. I don't know why the HOOKS array in my mkinitcpio.conf just contains "base" :-?
    So, just before regenerate the ramdisk image I edit my /etc/mkinitcpio.conf and add all the neccessary hooks and generate. I can bring my Arch box back to life

  • [Solved] Can't boot, root device not found

    I recently performed an update of udev and my kernel and after this I am unable to boot the normal kernel or the fallback. When I try I get this error:
    ERROR: Unable to find root device '/dev/disk/by-uid/03619a2f-908f-4724-ba4b-1fb3985e382b' You are being dropped to a recovery shell Type 'exit' to try and continue booting sh: can't access tty; job control turned off
    Typing exit results in me dropping to another shell and if done repeatedly a kernel panic. I attempted to boot via the grub console using the sda device block but I came up with the same error. When I look in /dev through the recovery console that comes up the sda* blocks aren't present.
    I need to know if there is a way to do this without entirely reformatting my system, I also don't have easy access to another computer but I have an android phone. Any assistance is greatly appreciated.
    Last edited by Surry (2012-03-20 00:06:12)

    This has been solved.
    For anybody's reference:
    From the recovery shell I had to load the modules ahci and sd_mod and that got the sda* to appear in /dev. After that I had to mount /dev/sda3 (my root partition) under /root and /new_root and then enter 'exit' to continue booting.
    Pretty much:
    modprobe ahci
    modprobe sd_mod
    mount /dev/sda3 /root
    mount /dev/sda3 /new_root
    exit

  • Can built-in device to read/write SDHC cards 4-8-16 GB?

    I have Lenovo 3000 N200 laptop which has a multy card reader, but I wonder if it is capable of reading and writing those latest SDHC cards?
    I am planning to buy a such card for a HD-camcorder.

    If you are using a DSLR camera, like for example a Canon 60D, there may be an option to use a "Low-Level Formatting" on the card. This should make it writable when putting it into the computer.
    To test this (and confirm it works) I did the following:
    Hardware Used:
    Canon 60D camera body
    Sandisk 32GB SDHC Extreme Card
    Macbook Pro 15" (mid 2010 model) with built-in SD card slot.
    Steps:
    Place SDHC card into camera (SD card may work as well). Navigate through menu until you arrive at settings that allow the camera to format the card. There may be an option to format it "low-level", which you would then select.
    -Note that all files on card will be erased permanently.-
    After the camera formats, eject the card from the camera, and place inside the built-in SD slot on the Macbook.
    The card should automatically mount, containing both read and write priviledges.
    Hope that helps.
    ~Charlie~
    Owner/Founder HotTips! LLC
    http://hottipscentral.com

  • Audio devices not reading Iphone 5

    I recently converted from Iphone 3SG to 5.  Now my car stereo (Kenwood) or home stereo (Pioneer) will not stream music.  How can I fix this issue?

    I read a very long thread about this (you can search for it) and the gist was that it's poor programming on the part of Pioneer and other vendors. Apple changed the BT on new devices but it is still backwards compatible. However, ithat backward compatibility only works if the other BT device meets the complete BT spec.
    Some manufacturers have released new firmware to address the problem. Don't look to Apple for a solution because I don't think it's their problem.

  • Mount point won't allow read/write for non-root user

    Any ideas why this particular fstab line leads to root user only read/write for any disk referenced in my fstab?
    Example:
    UUID=496E-7B5E   /media/STORAGE   vfat   defaults 0   0
    I have tried all variations of what "defaults" should be (rw,suid,dev,exec)
    I had even added uid=0777, and no matter what options I add there, doing
    sudo mount -a
    or with the line in fstab commented out and
    mount -t vfat -U 496E-7B5E /media/STORAGE -o defaults
    causes the same issue.
    Results in every filesystem there to be mounted as read only for me as a user, and I can only write to them as root. 
    Weird
    I have run
    sudo chmod -v -R a+rwx /media/STORAGE
    and similarly
    sudo chmod -v -R 0777 /media/STORAGE
    Both were tried on the directory as mounted and unmounted.  When mounted, the verbose output DOES NOT error out and shows property change of the files
    Oddly, if no fstab reference is used, the disk shows up in the dolphin panel, and can be mounted in that manner and it is read write as a usual user. 
    Using a Chakra-live installed with Unetbootin, so perhaps that is the issue... so
    How is mounting through dolphin handled and what might I use at the command line to accomplish this same routine, as I only need one partition to mount read write when the system starts, so maybe I can add the command to rc.local
    Last edited by bwh1969 (2009-01-18 23:04:59)

    # fstab generated by gen_fstab
    #<file system>   <dir>         <type>      <options>    <dump> <pass>
    none            /dev/pts      devpts      defaults        0     0
    none            /dev/shm      tmpfs       defaults        0     0
    UUID=496E-7B5E /media/STORAGE vfat    defaults,user,users,rw,exec,uid=777,gid=777   0       0
    /dev/sr0     /mnt/sr0_cd  auto     user,noauto,exec,unhide 0     0
    # This would do for a floppy
    #/dev/fd0        /mnt/floppy    vfat,ext2 rw,user,noauto    0     0
    #    +   mkdir /mnt/floppy
    # E.g. for USB storage:
    #/dev/sdb1        /mnt/usb      auto      rw,user,noauto   0     0
    #    +   mkdir /mnt/usb

Maybe you are looking for

  • Error running a Copy Package from BPF (BPC7.5)

    Hi all, I'm on BPC75 NW SP09, and Iu2019m trying to run the standard u201CCopyu201D package through BPF but it gives me following error message: IMMEDIATE RUN: Error occurred while trying to run the package on the server Data not found in table (UJD_

  • Wine + idtech3 = faulty search path?

    i was trying some games installed on W7 (dual boot) via Wine. now, the majority of them work, but here are some exceptions: every game based on the idtech3 engine. i know they're all compatible with Wine (also know there are linux versions of them, b

  • Bapi /  FM to create VL01N

    any Bapi /  Fm to create DO

  • Multiple Infotype operation in simulation mode

    Hi All, We have a requirement to first delete a infotype record and then add another record in simulation mode or to add multiple new record in simulation. Can you please let me know how to implement this functionality. Thanks in advance. Srikanta

  • CSAP_MAT_BOM_MAINTAIN  Alternative ?

    Hi Friends , I would like to know if there is a BAPI i can use instead of CSAP_MAT_BOM_MAINTAIN. I want to try using a BAPI because this function module is causing change in  the ECM number of the other vairant BOMS which were not intended to be chan