ENCUMBRANCE ENTRIES FOR REQUISITION WITH PARTIAL RESERVE STATUS?

Hi,
On 11.5.10.2 in Production:
When a Purchase Requisition (PR) is created with 2 distributions with 2
different budget a/c and one account having sufficient funds and other one
not having funds,
Now reserved he PR which was showing the Budgetary control exception -
Line 1 Distribution 1 fails funds check
Line 1 Distribution 2 passes funds check
In this case will that document is eligible to forward to the next manager for approval or will the document remains in “Incomplete” status.
If that document is forward to the next manager for approval what was the reason behind that…?
Please let me know..
Regards,
Kv.
Edited by: Peter.Kv on Oct 25, 2009 9:34 PM

Hi all,
the problem was that the relation between plant and product was somehow mixed up. We created it new and now we can process the mesasges.
But i have one more questions, which Monitoring Transactions i have for SRM (Abap/Portal)? When I was in Debug Mode i saw error Messages like:
A     /SAPSRM/CH_SOA_MSG     84     Purchasing group for follow-on document missing
A     BBP_PD     245     Purchasing group for follow-on document missing
A     BBP_PD     246     Purchasing organization for follow-on document missing
A     BBP_PD     249     Document type for determined backend system missing
E     BBP_PC     13     No default value is defined
E     BBP_PC     22     No tax data maintained
E     BBP_PD     276     Back-end data could not be read
E     BBP_PD     358     Select a location that is assigned to the plant chosen
E     BBP_TAX     1     Tax code could not be determined
E     BBP_TAX     13     Not possible to calculate tax
But i only saw that in the monitoring? These Errors can happy every time and i need to see them.... can you please tell me, where i can have a look?

Similar Messages

  • Goods Receipt entry for items with serial number

    Hi All,
    When I try to create a Goods receipt entry, for items with serial number, i'm always getting the following error message.
    [OSRI] , 'The selected quantity of serial/batch numbers is greater than the quantity in row Id'
    The following is the code that I'm using
    Dim oInvetoryGenEntry As SAPbobsCOM.Documents
    Dim oSerialNumber As SAPbobsCOM.SerialNumbers
    Dim ErrCode As Long
    Dim ErrMsg As String
    Dim ret As Long
    Set oInvetoryGenEntry = oCmp.GetBusinessObject(oInventoryGenEntry)
    Set oSerialNumber = oInvetoryGenEntry.Lines.SerialNumbers
    oInvetoryGenEntry.DocDate = Now
    oInvetoryGenEntry.DocRate = 1
    oInvetoryGenEntry.TaxDate = Now
    oInvetoryGenEntry.PaymentGroupCode = "3"
    oInvetoryGenEntry.Comments = "GRN Entry11"
    oInvetoryGenEntry.Lines.ItemCode = "A00004"
    oInvetoryGenEntry.Lines.Price = 100
    oInvetoryGenEntry.Lines.Quantity = 1
    oSerialNumber.SystemSerialNumber = 55555
    oSerialNumber.InternalSerialNumber = "2354"
    oSerialNumber.BatchID = "bt1"
    oSerialNumber.Add
    ret = oInvetoryGenEntry.Add
    If ret <> 0 Then
            oCmp.GetLastError ErrCode, ErrMsg
            MsgBox ErrCode & " " & ErrMsg
        Else
            MsgBox "GRN Entry made."
        End If
    It would be wonderful if anyone help me out to trace the exact reason for this issue.
    Thanks
    John

    Hi John I'm almost sure that your working with SDK 6.5 with SP1 or lower, visit this address
    https://www.sdn.sap.com/sdn/collaboration.sdn?node=linkFnode6-1&contenttype=url&content=https://DI: Add more than one serial numbers in Invoice
    Maybe you can find your answer if you can fix it let me Know my email address is [email protected] because i had the same problem.
    Regards

  • Settlement of WBS with Partially Released status

    Hi colleagues,
    We are encountering problems during our settlement to AUC. Although the settlement rule is maintained, the system does not allow us to post the settlement to a WBS with "PREL" (partially released) status. Is this really the standard of the system? When can we release the WBS?
    Thank you.

    Ask your FICO consultants to create a separate Asset class for AUCs.
    They can maintain such class in OAOA, where ask them to maintain status of Auc as Investment Measure.
    Now you can use this class in OITA - Investment Profile.
    And assign this Investment Profile to Project Profile in OPSA.
    Assign this Profile to capital project.
    Now all your assets which are AUC stage will come to this asset class.
    You can create completed asset in the other class by full settlement.
    Rewards for helpful answer.
    Thanks,
    RIYA

  • Cash Position - Entry for accounts with balance zero

    Hello Guru,
    is there a possibility to see in my cash position one entry for each account, which is included in the structure, even if the balance of the corresponding account is zero. At the moment I get no entry for accounts whose balances are zero.
    Best regards
    Phillip

    I had posted a OSS note for the above question and SAP says that the  FF7A report with the option 'Delta display' will (that is SAP's intention) display 'with balance' in the first and last column and 'without balance' in the other columns.
    So when we run the report today we should use 'Current day minus 1' in the 'display as of ' field. so that in the second column we can see today's transactions without balance. That works for me.
    Thanks to all who replied to my posting.
    Kalyan.

  • Credit Check not occurring for Customer with Partial Credit limit existing

    Hi,
    I have a scenario
    1) where, if credit limit is crossed, then on creation of order I get an credit check even when i have not entered materials in sales order.
    2) Partial Credit limit is pending (for e.g Credit limit of 100, 50 is still pending) when i create a new order with unconfirmed quantity, for amount 100, there is no credit check happening. (system should give message for extra amount 50)
    Can I please get guidance on this issue.(2nd point)
    Thanks & Regards,
    Ganesh.

    HI Ganesh,
    Your issue is not clear. What do you mean by
    2) Partial Credit limit is pending (for e.g Credit limit of 100, 50 is still pending) when i create a new order with unconfirmed quantity, for amount 100, there is no credit check happening. (system should give message for extra amount 50)
    Please explain clearly
    Thanks
    Jobi

  • Accounting Entries for Consignment - with CIN Entries

    Following are steps in consignment sale:
    1. Consignment Fill-Up (From factory to consignment agent)
    2. Consignment Issue (From consignment to end customer)
    3. Consignment Pick up
    4. Consignment Returns
    I searched in SDN forums. It says that there is no account entries at the time of consignment fill up.
    But I want accounting entries in at the time of 'consignment fill up' also.
    Entry should be:
    Consignee A/c ... Dr (Customer)
       To Consignment Sales contra A/c
    Excise Duty Paid A/c.. Dr
       To Excise Duty Payable A/c.
    At the time of issue:
    Delivery:
    Cost of Goods Sold A/c.. Dr
       To Inventory A/c
    Billing:
    Consignee A/c.. Dr (Customer)
       To Sales A/c
       To VAT Payable A/c
    Please help how can i get above entries entries?
    Will I have to create two distribution channel for hitting Consignment sales contra A/c (in step1) and Sales A/c (in sept 2)

    As you are aware even in normal sales, only when you generate a commercial invoice, customer will get debited.  But in the consignment fill up process, you only generate F8 delivery related proforma and hence, your requirement cannot be achieved.
    G. Lakshmipathi

  • Unable to make entries for objects with no master data in IP

    Hi All,
    In BPS, when created a layout, which contains characteristics, in whose properties 'Master Data' is not checked, we could enter the new values for them directly in the layout.
    In IP, we could not do the same with the 'New Lines" option set on Analysis Item in the WAD for the characteristics whose master data property is not checked.
    We have a layout, where, some characteristics are having master data checked, and some other characteristics where master data is not checked.
    With the 'New Lines' option set on Analysis Item in the WAD for the characteristics whose master data property is not checked, when data entered, the error message is appearing saying that the data is not valid.
    This is so quite simple in BPS. I think, I might be missing something in IP on how to achieve this.
    Thanks in Advance,
    Best Regards,
    - Shashi

    Hi,
    In IP it's integerated that if you will not maintain master data you may not be able to plan for new value of characteristic.It's the normal behavior of system.
    Cna check the link below:-
    Master data planning in BI
    Hope it may be helpful

  • Delete purchase requisition with item category Subcontracting

    Hi all,
    I need to delete a purchase requisition with item category = L (subcontracting).
    I am using already BAPI_REQUISITION_DELETE to delete other purchase requisitions but for the subcontracting it doest not work. In fact in the BAPI code you can see:
    Requisitions with dependent reservations won't be processed
        IF xeban-pstyp EQ 3 AND xeban-rsnum NE space.
    So I am looking for other BAPI but I don't find any to delete this kind of requisitions. Do you know any way to do that or I have to do a batch input?
    Thx,
    Manel

    Hi Manel,
    I am using BAPI_PO_CHANGE to set EBAN_EBAKZ, however in most of the cases error thrown as "Instance PO Number of object type  could not be changed".
    Could you please help on this?
    Thanks,
    Murali

  • Issues with GPO for Open With/Folder Type

    Hello,
    We have a mixed environment of x86 and x64 Windows 7 systems. We are using Windows Server R2 Group Policy. We want to associate certain type of file to open with Excel. In user configurations\Preferences\Folder Options,  I added two entries to associate
    the file type to open with Excel. One entry for x86 with correct path to Excel.exe and the other the same way for x64 systems. What I have found though is that 2nd entry is the only one that applies to ALL systems. This changes the Registry key HKEY\Classes\Root\Applications\Excel.exe.
    Therefore, the 32 bit systems receive that GPO with the wrong path to open these files with Excel so it doesnt work.
    1. How can I avoid this so that all systems open the file type with Excel, regardless if they are x86 or x64?
    2. Why does it allow you to enter muliple lines in the Folder Options, but only apply one of them to everyone?
    Thanks

    > 1. How can I avoid this so that all systems open the file type with
    > Excel, regardless if they are x86 or x64?
    Click "common", item level targeting. Target for Environment variable
    "PROCESSOR_ARCHITECTURE", value "AMD64" or "X86".
    > 2. Why does it allow you to enter muliple lines in the Folder Options,
    > but only apply one of them to everyone?
    Both apply to everyone, but the second overwrites the first if you do
    not use item level targeting.
    Martin
    Mal ein
    GUTES Buch über GPOs lesen?
    NO THEY ARE NOT EVIL, if you know what you are doing:
    Good or bad GPOs?
    And if IT bothers me - coke bottle design refreshment :))

  • How to Control authorization for users with certain status for level 2 WBS Element

    Dear All,
    Is there any standard way or enhancement available to control authorization for users with certain status for WBS Element i.e. for example
    Pre-requisite:
    There is only 2 level of project i.e.
    Lev_ WBSE_______Description
    1___ 7-14.E_______summay outage controller
    2___ 7-14.E.2310__ Plant/unit # 2310
    2___ 7-14.E.2310__ Plant/unit # 2220
    Project Controller  (authorization role assigned "Z_PS_OP7_OTGCON_C") have all project level authorization
    Plant/Unit Controller (authorization role assigned "Z_PS_OP7_PLNTOTG_C_2310") have only level 2 authorization with enhancement that we did in system by Z table.
    User ID_ Plant #
    123345_ 2310
    122455_ 2220
    Issue:
    After System Status released and User Status approved the WBS basic date for Plant/Units should be restricted from updating/changing by Plant/Unit Controller level and only project controller should have this authority.
    Solution required: 
    Can any one tell how to control this scenario either by standard or enhancement available to control authorization
    BR
    Saqib Usman   

    Hi,
    Did you explore SAP Enhancement CNEX0002 Using Transaction CMOD?
    Thank you and regards,
    Varshal Kachole
    The SCN Rules of Engagement

  • [SOLVED] Need help with rEFInd boot entry for rsync backup

    I made a successful backup my arch install to an other internal SSD disk (from my HDD).
    But now I can't figure out how to make a boot entry for this drive. The wiki only mentions GRUB, which I do not use.
    This is the fstab for my HDD:
    # <file system> <dir> <type> <options> <dump> <pass>
    # /dev/sda5
    UUID=c1822e3c-e037-4445-bdd8-b71778237dee / ext4 rw,relatime,data=ordered 0 1
    # /dev/sda2 LABEL=SYSTEM_DRV
    UUID=D2DF-9F74 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
    And this is the fstab on my SSD which I edited:
    # <file system> <dir> <type> <options> <dump> <pass>
    # /dev/sdb1
    UUID=c61a1301-4728-465d-b40b-bde5e084eb50 / ext4 rw,relatime,data=ordered 0 1
    # /dev/sda2 LABEL=SYSTEM_DRV
    UUID=D2DF-9F74 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
    But I'm not sure about the /boot entry, do I need something else here?
    Afterward I tried updating rEFInd by reinstalling using refind-install, but that did not work.
    ps. I dual boot with Windows.
    Last edited by Devenda (2014-08-18 07:58:07)

    I also tried adding the menu entry manually by editing refind.conf but that didn't work. I got:
    Invalid loader file!
    Error: Not Found while loading vmlinuz-linux
    Here is some additional info:
    refind.conf:
    menuentry "SSD Arch Linux" {
    icon /EFI/refind/icons/os_arch.png
    volume "ArchSSD"
    loader /boot/vmlinuz-linux
    initrd /boot/initramfs-linux.img
    options "root=/dev/sdb1 ro"
    I hope this helps.
    blkid
    /dev/sda1: LABEL="WINRE_DRV" UUID="7C2ADD1D2ADCD4EC" TYPE="ntfs" PARTUUID="b7137819-2ca6-40fb-9167-b73ac37d8d96"
    /dev/sda2: LABEL="SYSTEM_DRV" UUID="D2DF-9F74" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="9c77b526-730f-42f9-9904-f9a31b205687"
    /dev/sda3: PARTLABEL="Microsoft reserved partition" PARTUUID="f4d5275b-24c1-4847-b937-345bc23bec89"
    /dev/sda4: LABEL="Windows 8" UUID="38D6E449D6E408C8" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="d777a359-f42c-4629-a07c-cc55316352fe"
    /dev/sda5: UUID="c1822e3c-e037-4445-bdd8-b71778237dee" TYPE="ext4" PARTUUID="3d282004-2515-4630-b82e-35ed7f707b89"
    /dev/sda6: UUID="F80680CC06808D76" TYPE="ntfs" PARTUUID="575bc623-c7f1-44da-a79e-220ce3c98d9b"
    /dev/sda7: LABEL="Lenovo_Recovery" UUID="0898D76B98D75632" TYPE="ntfs" PARTUUID="99bfc6d6-1b71-46d1-887e-2f7e65e3eab1"
    /dev/sdb1: LABEL="ArchSSD" UUID="c61a1301-4728-465d-b40b-bde5e084eb50" TYPE="ext4" PARTUUID="e87704a5-01"
    lsblk -f
    NAME FSTYPE LABEL UUID MOUNTPOINT
    sda
    ├─sda1 ntfs WINRE_DRV 7C2ADD1D2ADCD4EC
    ├─sda2 vfat SYSTEM_DRV D2DF-9F74 /boot
    ├─sda3
    ├─sda4 ntfs Windows 8 38D6E449D6E408C8
    ├─sda5 ext4 c1822e3c-e037-4445-bdd8-b71778237dee /
    ├─sda6 ntfs F80680CC06808D76
    └─sda7 ntfs Lenovo_Recovery 0898D76B98D75632
    sdb
    └─sdb1 ext4 ArchSSD c61a1301-4728-465d-b40b-bde5e084eb50
    sr0
    boot tree
    /boot
    ├── BOOT
    │   └── boot.sdi
    ├── BOOTSECT.BAK
    ├── EFI
    │   ├── Boot
    │   │   ├── bootx64.efi
    │   │   ├── LenovoBT.EFI
    │   │   ├── License.txt
    │   │   └── ReadMe.txt
    │   ├── gummiboot
    │   │   └── gummibootx64.efi
    │   ├── Lenovo
    │   │   └── Boot
    │   │   ├── BCD
    │   │   ├── BCD.LOG
    │   │   ├── BCD.LOG1
    │   │   ├── BCD.LOG2
    │   │   ├── bg-BG
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── bootmgfw.efi
    │   │   ├── bootmgr.efi
    │   │   ├── BOOTSTAT.DAT
    │   │   ├── boot.stl
    │   │   ├── cs-CZ
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── da-DK
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── de-DE
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── el-GR
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── en-GB
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── en-US
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── es-ES
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── et-EE
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── fi-FI
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── Fonts
    │   │   │   ├── chs_boot.ttf
    │   │   │   ├── cht_boot.ttf
    │   │   │   ├── jpn_boot.ttf
    │   │   │   ├── kor_boot.ttf
    │   │   │   ├── malgun_boot.ttf
    │   │   │   ├── malgunn_boot.ttf
    │   │   │   ├── meiryo_boot.ttf
    │   │   │   ├── meiryon_boot.ttf
    │   │   │   ├── msjh_boot.ttf
    │   │   │   ├── msjhn_boot.ttf
    │   │   │   ├── msyh_boot.ttf
    │   │   │   ├── msyhn_boot.ttf
    │   │   │   ├── segmono_boot.ttf
    │   │   │   ├── segoen_slboot.ttf
    │   │   │   ├── segoe_slboot.ttf
    │   │   │   └── wgl4_boot.ttf
    │   │   ├── fr-FR
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── hr-HR
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── hu-HU
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── it-IT
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── ja-JP
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── ko-KR
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── lt-LT
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── lv-LV
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── memtest.efi
    │   │   ├── nb-NO
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── nl-NL
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── pl-PL
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── pt-BR
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── pt-PT
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── qps-ploc
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── Resources
    │   │   │   ├── bootres.dll
    │   │   │   └── en-US
    │   │   │   └── bootres.dll.mui
    │   │   ├── ro-RO
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── ru-RU
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── sk-SK
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── sl-SI
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── sr-Latn-CS
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── sv-SE
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── tr-TR
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── uk-UA
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── zh-CN
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── zh-HK
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   └── zh-TW
    │   │   ├── bootmgfw.efi.mui
    │   │   ├── bootmgr.efi.mui
    │   │   └── memtest.efi.mui
    │   ├── Microsoft
    │   │   └── Boot
    │   │   ├── BCD
    │   │   ├── BCD.LOG
    │   │   ├── BCD.LOG1
    │   │   ├── BCD.LOG2
    │   │   ├── bg-BG
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── bootmgfw.efi
    │   │   ├── bootmgr.efi
    │   │   ├── BOOTSTAT.DAT
    │   │   ├── boot.stl
    │   │   ├── cs-CZ
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── da-DK
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── de-DE
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── el-GR
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── en-GB
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── en-US
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── es-ES
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── et-EE
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── fi-FI
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── Fonts
    │   │   │   ├── chs_boot.ttf
    │   │   │   ├── cht_boot.ttf
    │   │   │   ├── jpn_boot.ttf
    │   │   │   ├── kor_boot.ttf
    │   │   │   ├── malgun_boot.ttf
    │   │   │   ├── malgunn_boot.ttf
    │   │   │   ├── meiryo_boot.ttf
    │   │   │   ├── meiryon_boot.ttf
    │   │   │   ├── msjh_boot.ttf
    │   │   │   ├── msjhn_boot.ttf
    │   │   │   ├── msyh_boot.ttf
    │   │   │   ├── msyhn_boot.ttf
    │   │   │   ├── segmono_boot.ttf
    │   │   │   ├── segoen_slboot.ttf
    │   │   │   ├── segoe_slboot.ttf
    │   │   │   └── wgl4_boot.ttf
    │   │   ├── fr-FR
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── hr-HR
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── hu-HU
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── it-IT
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── ja-JP
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── ko-KR
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── lt-LT
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── lv-LV
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── memtest.efi
    │   │   ├── nb-NO
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── nl-NL
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── pl-PL
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── pt-BR
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── pt-PT
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── qps-ploc
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── Resources
    │   │   │   ├── bootres.dll
    │   │   │   ├── en-US
    │   │   │   │   └── bootres.dll.mui
    │   │   │   └── nl-NL
    │   │   │   └── bootres.dll.mui
    │   │   ├── ro-RO
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── ru-RU
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── sk-SK
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── sl-SI
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── sr-Latn-CS
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── sr-Latn-RS
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── sv-SE
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── tr-TR
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── uk-UA
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── zh-CN
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── zh-HK
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   └── zh-TW
    │   │   ├── bootmgfw.efi.mui
    │   │   ├── bootmgr.efi.mui
    │   │   └── memtest.efi.mui
    │   ├── refind
    │   │   ├── icons
    │   │   │   ├── arrow_left.png
    │   │   │   ├── arrow_right.png
    │   │   │   ├── boot_linux.png
    │   │   │   ├── boot_win.png
    │   │   │   ├── func_about.png
    │   │   │   ├── func_exit.png
    │   │   │   ├── func_firmware.png
    │   │   │   ├── func_reset.png
    │   │   │   ├── func_shutdown.png
    │   │   │   ├── os_altlinux.png
    │   │   │   ├── os_arch.png
    │   │   │   ├── os_centos.png
    │   │   │   ├── os_chrome.png
    │   │   │   ├── os_clover.png
    │   │   │   ├── os_debian.png
    │   │   │   ├── os_ecomstation.png
    │   │   │   ├── os_fatdog.png
    │   │   │   ├── os_fedora.png
    │   │   │   ├── os_freebsd.png
    │   │   │   ├── os_freedos.png
    │   │   │   ├── os_funtoo.png
    │   │   │   ├── os_gentoo.png
    │   │   │   ├── os_gummiboot.png
    │   │   │   ├── os_haiku.png
    │   │   │   ├── os_hwtest.png
    │   │   │   ├── os_kubuntu.png
    │   │   │   ├── os_legacy.png
    │   │   │   ├── os_linuxmint.png
    │   │   │   ├── os_linux.png
    │   │   │   ├── os_lubuntu.png
    │   │   │   ├── os_mac.png
    │   │   │   ├── os_mageia.png
    │   │   │   ├── os_mandriva.png
    │   │   │   ├── os_manjaro.png
    │   │   │   ├── os_mythbuntu.png
    │   │   │   ├── os_netbsd.png
    │   │   │   ├── os_openbsd.png
    │   │   │   ├── os_opensuse.png
    │   │   │   ├── os_redhat.png
    │   │   │   ├── os_refind.png
    │   │   │   ├── os_refit.png
    │   │   │   ├── os_slackware.png
    │   │   │   ├── os_suse.png
    │   │   │   ├── os_ubuntu.png
    │   │   │   ├── os_unknown.png
    │   │   │   ├── os_win.png
    │   │   │   ├── tool_apple_rescue.png
    │   │   │   ├── tool_memtest.png
    │   │   │   ├── tool_mok_tool.png
    │   │   │   ├── tool_part.png
    │   │   │   ├── tool_shell.png
    │   │   │   ├── tool_windows_rescue.png
    │   │   │   ├── transparent.png
    │   │   │   ├── vol_external.png
    │   │   │   ├── vol_internal.png
    │   │   │   └── vol_optical.png
    │   │   ├── icons-backup
    │   │   │   ├── arrow_left.png
    │   │   │   ├── arrow_right.png
    │   │   │   ├── boot_linux.png
    │   │   │   ├── boot_win.png
    │   │   │   ├── func_about.png
    │   │   │   ├── func_exit.png
    │   │   │   ├── func_firmware.png
    │   │   │   ├── func_reset.png
    │   │   │   ├── func_shutdown.png
    │   │   │   ├── os_altlinux.png
    │   │   │   ├── os_arch.png
    │   │   │   ├── os_centos.png
    │   │   │   ├── os_chrome.png
    │   │   │   ├── os_clover.png
    │   │   │   ├── os_debian.png
    │   │   │   ├── os_ecomstation.png
    │   │   │   ├── os_fatdog.png
    │   │   │   ├── os_fedora.png
    │   │   │   ├── os_freebsd.png
    │   │   │   ├── os_freedos.png
    │   │   │   ├── os_funtoo.png
    │   │   │   ├── os_gentoo.png
    │   │   │   ├── os_gummiboot.png
    │   │   │   ├── os_haiku.png
    │   │   │   ├── os_hwtest.png
    │   │   │   ├── os_kubuntu.png
    │   │   │   ├── os_legacy.png
    │   │   │   ├── os_linuxmint.png
    │   │   │   ├── os_linux.png
    │   │   │   ├── os_lubuntu.png
    │   │   │   ├── os_mac.png
    │   │   │   ├── os_mageia.png
    │   │   │   ├── os_mandriva.png
    │   │   │   ├── os_manjaro.png
    │   │   │   ├── os_mythbuntu.png
    │   │   │   ├── os_netbsd.png
    │   │   │   ├── os_openbsd.png
    │   │   │   ├── os_opensuse.png
    │   │   │   ├── os_redhat.png
    │   │   │   ├── os_refind.png
    │   │   │   ├── os_refit.png
    │   │   │   ├── os_slackware.png
    │   │   │   ├── os_suse.png
    │   │   │   ├── os_ubuntu.png
    │   │   │   ├── os_unknown.png
    │   │   │   ├── os_win.png
    │   │   │   ├── tool_apple_rescue.png
    │   │   │   ├── tool_memtest.png
    │   │   │   ├── tool_mok_tool.png
    │   │   │   ├── tool_part.png
    │   │   │   ├── tool_shell.png
    │   │   │   ├── tool_windows_rescue.png
    │   │   │   ├── transparent.png
    │   │   │   ├── vol_external.png
    │   │   │   ├── vol_internal.png
    │   │   │   └── vol_optical.png
    │   │   ├── keys
    │   │   │   ├── altlinux.cer
    │   │   │   ├── canonical-uefi-ca.der
    │   │   │   ├── fedora-ca.cer
    │   │   │   ├── openSUSE-UEFI-CA-Certificate.cer
    │   │   │   ├── refind.cer
    │   │   │   └── SLES-UEFI-CA-Certificate.cer
    │   │   ├── refind.conf
    │   │   ├── refind.conf.old
    │   │   ├── refind.conf-sample
    │   │   └── refind_x64.efi
    │   └── tools
    ├── grub
    │   ├── grub.cfg
    │   └── grub.cfg.example
    ├── initramfs-linux-fallback.img
    ├── initramfs-linux.img
    ├── loader
    │   ├── entries
    │   │   └── arch.conf
    │   └── loader.conf
    ├── refind_linux.conf
    └── vmlinuz-linux
    refind_linux.conf
    "Boot with standard options" "ro root=UUID=c1822e3c-e037-4445-bdd8-b71778237dee quiet "
    "Boot to single-user mode" "ro root=UUID=c1822e3c-e037-4445-bdd8-b71778237dee quiet single"
    "Boot with minimal options" "ro root=UUID=c1822e3c-e037-4445-bdd8-b71778237dee"

  • Setup to leave requisition for outside processing in 'Incomplete' status

    We are trying to implement outside processing, and the requisitions are automatically generated, but they are all in Approved status. Is there any setup/ profile option I can set to leave the requisitions in Incomplete status? Thanks

    I don't think it was using WF. When the work order was released, Oracle inserted the data immediately into the po_requisitions_interface_all and then launched the requisitions import program. But when it inserted the record, it inserted with the authorization_status as 'Approved'. So when the requisition import ran it created the requisition with approved status.
    There is a profile option INV: Minmax Reorder Approval that can control the status of the requisitions created using minmax. I thought there might be a profile option to control the status of requisitions created using outside processing, but seems like it does not exist.
    Another solution would be to create a trigger on the po_requisitions_interface_all table to set the status to 'Incomplete' for all requsiition lines. Since we have a policy to create requisitions iin ncomplete status by any automated processes it might work.
    Thanks for the ideas and feedback.

  • Can someone tell me how to create accounting entries with the account status as error

    Hi,
    Can someone tell me how to create accounting entries with the
    account status as error?
    Thanks!!
    Danny

    It's call fixed/static background, and it is NOT directly support by iweb, you will need post processing either in html or javascript.
    Varkgirl (you need to search the previous forum) and I did it since iweb1:
    try Safari, and scroll: http://www.geocities.com/[email protected]/Links.html
    invisible link? roddy, fishing for info again?

  • Partial goods receipt for PO with multiple line items

    Hello All,
    While doing MIGO, for a PO with multiple line items, if one line item is having error, will we be able to go ahead with goods receipt? Or entire material document is blocked for doing MIGO?
    We will be doing a development - in case if there is problem in goods receipt (checking of any parameter, and if it is missing - we will be posting error message)...is it possible to ahead with next line item and still post the material document?
    If partial goods receipt if possible for PO with multiple line items, how do we do it?
    Regards,
    RJS

    Hi
    While doing MIGO, for a PO with multiple line items, if one line item is having error, will we be able to go ahead with goods receipt? Or entire material document is blocked for doing MIGO?
    No. You cannot post the MIGO, if even one of the PO line item is having problem or giving error.
    We will be doing a development - in case if there is problem in goods receipt (checking of any parameter, and if it is missing - we will be posting error message)...is it possible to ahead with next line item and still post the material document?
    If you skip a line irem and do GR with next line item, how will you match quantity & value with the vendor Invoice at LIV ?
    If partial goods receipt if possible for PO with multiple line items, how do we do it?
    Partial goods receipt is possible for PO line items. That means, if PO has 100 qty for line item 1 then you can do GR for 50 now and 50 later depending on the vendors delivery.
    Hope this is what you mean by "Partial Goods Receipt".
    Edited by: Arun R on May 10, 2010 2:03 PM

  • LZW algorithm for data compression with partial clearing

    hello,
    i want to implement zip utility and in that i have to develop LWZ algorithm with partial clearing i.e unshrinking method in JAVA
    i am not getting information anout unshrinking on net.
    please anyone can help me.

    LZW had patent issues, so was replaced. I assume you don't want patent issues.
    The new algorithm is already programmed for you via the Inflater and Deflater classes in java.util.zip. Unfortunately the doc is nearly incomprehensible. Fortunately for you several of us have worked together and got it to work. Go to Advanced Language Topics and search for topics on Inflater. I've posted code there that is dead simple to use and would be a good foundation for any zip-like utilities.

Maybe you are looking for