Set-up of DRP

Hello,
Does anybody have a simple guide with some screen shots on how to set-up DRP?
I wanted to run DRP for 3 items in a test environment but it took all items that are in the MDS (over 2000).
Do I have to set-up a new inventory Org or is it sufficient to add the items to a specific subinventory?

Hi,
House bank definition includes several configuration items: you have to define house bank itself, the accounts determination, new G/L accounts, even SWIFT entry sometimes. So, you will have to automate a lot of operations; I wouldn't say it's efficient.
Regards,
Eli

Similar Messages

MRP creating cancel notices for min max purchased items

We use min max planning for many repetitive purchased items. These same items are also set to MPS/DRP Planned as well. This is only so we can use the Planned Order report to identify material shortages to flow schedules.
However, MRP exceptions is requesting we cancel our min max purchased items since there is no demand. Can MRP be modified to NOT include min max planning method in cancel requests?
If not, where can I find a tool to identify material shortages for flow schedules?

Many thanks for this.
I can see entirely why it's designed as such, but I just find it slightly frustrating that there's no way to break the link between the order and the shipment out to the depot. Just to clarify, we're not requiring the orders to change - they will still be made and will come in - but just that the orders themselves don't specifically need to be the stock that is used for the replenishment.
So -
1. Min Max identifies depot needs replenishing.
2. Central distribution does not have (enough) stock to replenish.
3. Order is made to replenish central distributions stock.
4. We ship whatever we've got, when we've got it, to depot to replenish.
It's the bit where Min-Max is trying to replensih a specific depot rather than our central distribution centre that's my problem.
I suspect that, as you say, that specific issue is not directly fixable without getting our IT contractors to do a customisation.
I'm going to look into your Supply Date Offset suggestion now, though I'm not sure how this affects the shipping after the orders are placed. The orders themselves are approved manually after we've checked our stock position (i.e. what's in with the recycling team), but we recycle & refurb probably 60% of our maint stock so there'll always be kit turning up after the order has been made because of the long lead times.
Thanks again.

DRP settings significance in SAP R/3

Hi All,
As per client requirement, we need to change the below settings:
SPRO> Prodution>Basis Settings> Maintain assignment of Node Type- Plant
We are using the SAP R/3 alone and no APO. Here for few plants new node type need to be assigned and for few it need to be changed. Please let me the impact of changing this settings in SAP/R3. Also if this program is used anywhere in standard report.
Thanks in advance.

I think you don't have to worry if you are not using APO.
As per my knowledge it basically used during creation of data in APO,
When you generate integration model, CFM1 transaction would allow you to select the relevant location types only. Meaning that when you select plant, you are able to select only the plants, and not customer or vendor, for example.
To specify in R/3 that a particular plant is a DC, you need to matain customization in SPRO at below location:
Production-> Distribution Resource Planning (DRP)->Basic Settings-> Maintain assignment of node type - plant
Give node type as DC in the above SPRO setting for the DC. For the plant, you don't maintain this setting.
During CIF, CIF interface would recongnize this SPRO setting and create a DC in APO after CIF.
Plant will be created as plant.
But why you want to make changes in node type?

Not able to see more than one period in DRP Planning Book

Hi
Where do we set the no of periods( days, weeks etc) that should be visbile in the DRP planning book in the SAP SPP.
Also we are getting invalid periodicity in this planning book, when we select one of the available timebucked profile ids. Any clues on this ? How to set it correct?
Regards,

i think like in any other planning book, it should be in the Data view tab in the TB future.
you need to create time bucket profiles though that have the periods you need. And these periods need to be equal to or greater than the Storage bucket profile used in the linked planning area

Deployment - setting for system not to create planned orders.

hi
I am executing deployment at the plant level.
i have req. of 8000 on 26th and 9000 on 27th.
i created a stock of 3000 on 25th.
i am executing push deployment and maintained setting accordingly.
After completion of deployment, system deploys the stock ie 3000 and creates Planned order for the remaining 5000 to meet the demand of 8000.
What setting has to be maintained such that system only deploys 3000 or the stock only and does not create a planned order for the unful filled demand. ???
in onther words system should deploy the stock and should not do anything more than that.
Thanks.

Hi Aswath,
Can you answer these few questions for me? I will be able to answer your more appropriately.
What is the order of planning runs in your system?
1. DPR for demand at DC that creates distribution demand at the plant
2. Deployment of the current stock at the plant
3. Planning run at the plant to create planned order for any demand left out
Is that the order? This does not make good sense for me but I don't know your scenario.
What kind of deployment run are you suing? deployment heuristics or optimizer?
In both the cases, you have "delete" and "reduce" option.
The system deploys the stock at the DC based on the distribution demand ( coming from DC to Plant).
If you use delete option, the system deploys for the amount of stock it has and deletes the remaining distribution demand.
So, if you got distribution demand of 100 PCs, there is only 50 PCs stock at plant, the plant deploys 50 and deletes the other 50 PCs distribution demand at the plant. You need to rerun DRP at DC if you want to get back this demand.
If you use reduce option, the system deploys for the amount of stock it has and reduces the remaining distribution demand.
So, if you got distribution demand of 100 PCs, there is only 50 PCs stock at plant, the plant deploys 50 and reduces the distribution demand at the plant to 50 PCs.
I think you have the second case and you are running planning run at the plant and it's creating orders. If you don't want the system to create them, use the "delete" option in deployment run.
Please let me know if I am getting your point right.

What pegging logic is used in ASCP 12.1 DRP plans?

Hi, could you help me to understand the folowing issue.
We are implementing ASCP 12.1 DRP planning and have issue with pegging - it's seemd to be done in random order. We need supplies are pegged to demands on day-by-day basis or "standard pegging" (select first supply peg to some demands in ascending order, then next supply peg to unpegged demands in ascending order, and so on). Peggind window for demands and supplies must be = 1 day, in supply windows supplies must be sorted by type before pegging (oh, firm, non-firm).
For example, see plan output:
Supply lines:
Org Item Order Type Sug Due Date Qty
1. Org1 item10 Purchase requisition 10.10.09 6
Pegging (Date/Qty): 10.10.09/1, 11.10.09/1, 12.10.09/2, 13.10.09/2
2. Org1 item10 Planned order 20.10.09 40
Pegging (Date/Qty): 19.10.09/2, 22.10.09/1, 23.10.09/2, 24.10.09/2, 25.10.09/1, 26.10.09/2, *14.11.09/2, 15.11.09/1, 17.11.09/2* ...
As mentioned in ASCP UG, there is folowing pegging methods:
1. FiFO
2. Standart
3. Priority
4. Priority|Standart
My profile setting is:
MSC: Use FIFO Pegging = No
MSO: Supply Window Size =1
MSO: Demand Window Size = 1
DRP plan has no options to switch pegging mode (while MDS/MPP/MRP has ones), so i could not guess witch mode DRP planning use and how to control it's logic.

Hi
ASCP Pegging Logic do not apply in DPP
in DPP The logic is allocation and you Control it with several Parameters:
Allocation Bucket (Daily, Weekly and Period )
Demand Priority Rule (different from ASCP)
Fare Share allocation Rules
Example Scenario:
Allocation Bucket (Period for example )
Demand Priority Rule:
Sales Order Major (Demand Class)
Sales Regular
Forecast
Within The allocation Bucket earliest supply will allocate Sales Order Majors (sorting By date)
Regards
Shlomi

Cannot set ringtones for people in my adress book

i have wiped handheld twice and still cannot set individual ringtones for people in my adress book that is different than the general ring was able too on my last phone and it was exact same phone

Hello rhwk118,
Welcome to the BlackBerry Support Community Forums.
Can you please clarify what model of the BlackBerry Smartphone you are currently using and the software version it is running. You can locate this info by going to Options>About (3rd line from the top) on your BlackBerry Smartphone.
Thank you
-DrP
Come follow your BlackBerry Technical Team on Twitter! @BlackBerryHelp
Be sure to click Kudos! for those who have helped you.
Click Solution? for posts that have solved your issue(s)!

Database deleted but have backup set

Hi
I have been doing some DRP testing & I have the backup set for a database. The test server has since been rebuilt. I have re-installed Oracle and now want to create a database using my backup set created by EM. Could anyone point me in the right direction to do this?
Thanks in advance!

You can try to adapt "Performing Disaster Recovery" scenario to your environment:
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmrecov.htm#i1006453
Edited by: P. Forstmann on 24 févr. 2010 10:39

SAP DRP (Distribution Resource Planning)

Dear All,
I have gone through the SAP DRP help. Can somebody explain with one example about DRP, where it is useful and how to process DRP in SAP PP. Any config settings to be done, How to set up distributuon network and How Deployement to be executed. Your help will be highly appreciable.
Thanks & Regards,
Ramagiri

Hi ,
There is a config under Prod--> DRP-->Basic setting-->Main assignment of node type-plant. here you can define Plant as B-Distribution center. There is no significance of this config.
Since you need plant to hold stock , Distribution center will be a plant object with node type defined in above config( Or you can implement MRP area , if you donot want to create more plants)
Either way ,
You have setup stock trasnfer between Plant(DC) & Plant using special procurement type(F-40) & system will generate Stock transfer PR which can be converted in Stock transfer PO
You can set up multiple key 41,42,43,44 for each plant(DC) pointing to differenet plant(Mfg)You can use this key in material master of Plant (DC) to define which plant will supply this material.
SAP MRP run is also deployment , it will plan Stock transfer PR based on demand entered on Plant(DC)
Hope it helps,
Jatin

JESD204B PHY missing DRP data port in "shared logic in example design" mode

Hi,
I have a JESD204B design with the PHY and core logic split. In addition, the PHY is *also* configured not to include common logic in the generated core. In practice, this means my RTL directly instantiates three blocks:
- the JESD204B core,
- the JESD204B PHY core, and
- the GTE2_COMMON core.
My purpose for splitting the GTE2_COMMON core out of the PHY is to debug a PLL reset issue -- my first question is: Are there known issues with the JESD204B IP failing to reset the QPLL? My system-level reset triggers rx_reset on the JESD204B core, but it does not appear to reset the QPLL.
My second question follows. The JESD204B PHY core includes a number of ports to drive DRP on the GTE2_COMMON core:
common0_drpaddr : OUT STD_LOGIC_VECTOR(7 DOWNTO 0);
common0_drpen : OUT STD_LOGIC;
common0_drpdo : IN STD_LOGIC_VECTOR(15 DOWNTO 0);
common0_drpwe : OUT STD_LOGIC;
common0_drprdy : IN STD_LOGIC;
However, I don't see a common0_drpdi port here to write data from the PHY to the DRP interface. It's odd that the write *enable* is present when the data itself isn't. Is this a flaw in the core, or am I missing something? Has the JESD204B IP been validated in this mode (separate PHY, separate GTE2_COMMON, using the QPLL, and including an AXI management bus)?
thanks,
Graeme

Hi Duncan,
Thanks for the response -- my first cut at this RTL connected *both* tx_reset_gt and rx_reset_gt on the PHY to the JESD204B core's rx_reset_gt output. In other words, a reset from the JESD204B core should have created both TX and RX resets in the PHY. It didn't appear to trigger QPLL resets that way. (This is how the example design is hooked up, too.)
I've traced the reset path through the PHY in Vivado's schematic viewer, and it does look like these resets play a role in QPLL resets -- though not an obvious role, and perhaps only during post-configuration initialization.
After some thought, it seems debateable whether tx_reset_gt or rx_reset_gt should be issuing QPLL resets at all. If the current behaviour is deliberate, I'd be content to toggle the QPLL power-down register for now. (I suspect the failure of the QPLL to lock reliably is due to my test set-up, and won't be present on production hardware anyhow.)
At any rate, I'd love to hear from Xilinx (1) if these reset signals can be used to trigger QPLL resets, and (2) if the JESD204B PHY is missing a DRP signal. (If so, I'd love to get that DRP port fixed in the next Vivado release or two.)
cheers,
Graeme

Recommendation on a good book on replenishment (DRP) using SAP SCM 5.0

Hi,
Appreciate that anyone can recommend a good, solid book on replenishment planning using SAP APO.
We don't find that SAP's documentation is helpful on replenishment planning of the global supply network, and it dos not seem to have a thoughtful design and well defined process. e.g. transport and shipment scheduling under the gATP documentation, which is clearly designed for sales order taking, and vaguely mentioned that the process can be apply for STR/STO. To me, it does not seem that author fully understand the entire supply chain planning process, from planning to execution in this regard. Another example, SAP documentation says that PP/DS heuristic can plan STR, but when you use it, then you realized that you really can not combine shipments and the planning process and execution are completely falling apart, as the scheduling dates, such like MAD, transport planning dates, pick/pack are not visible in APO nor integrated with planning process. out of sync with R/3. If using SNP, then we realized that the SNP heuristic is too simple to deal various different supply/demand situations, and have to adopt a completely different set of tools from production planning.
We have very tightly integrated global supply chain process for manufacturing, replenishment (DRP) and customer service. APO, having such sophisticated production planning functions, can not even handle such common marine transport planning well. We have both liquid and solid products with transport mode being marine, rail car, truck, barge etc. It is being a real challenge to plan our supply chain using APO.
Thank you in advance. Also appreciate anyone can share their experience.

Hi,
Check whether your Instance is up if not bring up the instance first. Try to logon to instance with DDIC user and reset the password to standard i.e 19920706.
Re-try the installation.
--Kishore

Xorg 1.10.1 no longer affected by manual DPI setting

I use my 23 inch 1920x1080 monitor as TV also. As this means I sit rather far from it, I manually set DPI quite low to enlarge windows and fonts by default. However after the last upgrade, which brought Xorg 1.10 and Gnome 3, Xorg seems to no longer be affected by my setting DPI in xorg.conf. The logs show that the value is read, and xdpyinfo shows the DPI I have set manually, but this setting no longer seems to affect any windows or fonts.
The DPI is set via the nvidia driver. Relevant parts of xorg.conf and the full Xorg.0.log are attached.
Does anyone know what could have caused this?
xorg.conf:
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
Option "DPI" "60x60"
EndSection
Xorg.0.log:
[ 45267.074]
X.Org X Server 1.10.1
Release Date: 2011-04-15
[ 45267.074] X Protocol Version 11, Revision 0
[ 45267.074] Build Operating System: Linux 2.6.38-ARCH x86_64
[ 45267.074] Current Operating System: Linux norstaurar 2.6.38-ARCH #1 SMP PREEMPT Fri May 13 09:24:47 CEST 2011 x86_64
[ 45267.074] Kernel command line: root=/dev/disk/by-uuid/41bd750d-271b-4392-898a-51e284889d43 ro
[ 45267.074] Build Date: 16 April 2011 12:02:01PM
[ 45267.074]
[ 45267.074] Current version of pixman: 0.20.2
[ 45267.074] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 45267.074] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 45267.074] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jun 3 10:40:17 2011
[ 45267.074] (==) Using config file: "/etc/X11/xorg.conf"
[ 45267.074] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 45267.075] (==) ServerLayout "Layout0"
[ 45267.075] (**) |-->Screen "Screen0" (0)
[ 45267.075] (**) | |-->Monitor "Monitor0"
[ 45267.075] (**) | |-->Device "Device0"
[ 45267.075] (**) |-->Input Device "Keyboard0"
[ 45267.075] (**) |-->Input Device "Mouse0"
[ 45267.075] (==) Automatically adding devices
[ 45267.075] (==) Automatically enabling devices
[ 45267.075] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 45267.075] Entry deleted from font path.
[ 45267.075] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 45267.075] Entry deleted from font path.
[ 45267.075] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 45267.075] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 45267.075] Entry deleted from font path.
[ 45267.075] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 45267.075] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/
[ 45267.075] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 45267.075] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 45267.075] (WW) Disabling Keyboard0
[ 45267.075] (WW) Disabling Mouse0
[ 45267.075] (II) Loader magic: 0x7d6fa0
[ 45267.075] (II) Module ABI versions:
[ 45267.075] X.Org ANSI C Emulation: 0.4
[ 45267.075] X.Org Video Driver: 10.0
[ 45267.075] X.Org XInput driver : 12.2
[ 45267.075] X.Org Server Extension : 5.0
[ 45267.076] (--) PCI:*(0:2:0:0) 10de:0848:1043:82f2 rev 162, Mem @ 0xfd000000/16777216, 0xf0000000/134217728, 0xfa000000/33554432, I/O @ 0x0000ec00/128, BIOS @ 0x????????/131072
[ 45267.076] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 45267.076] (II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
[ 45267.076] (II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
[ 45267.076] (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
[ 45267.076] (II) "record" will be loaded by default.
[ 45267.076] (II) "dri" will be loaded by default.
[ 45267.076] (II) "dri2" will be loaded by default.
[ 45267.076] (II) LoadModule: "dbe"
[ 45267.077] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 45267.077] (II) Module dbe: vendor="X.Org Foundation"
[ 45267.077] compiled for 1.10.1, module version = 1.0.0
[ 45267.077] Module class: X.Org Server Extension
[ 45267.077] ABI class: X.Org Server Extension, version 5.0
[ 45267.077] (II) Loading extension DOUBLE-BUFFER
[ 45267.077] (II) LoadModule: "extmod"
[ 45267.077] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 45267.077] (II) Module extmod: vendor="X.Org Foundation"
[ 45267.077] compiled for 1.10.1, module version = 1.0.0
[ 45267.077] Module class: X.Org Server Extension
[ 45267.077] ABI class: X.Org Server Extension, version 5.0
[ 45267.077] (II) Loading extension MIT-SCREEN-SAVER
[ 45267.077] (II) Loading extension XFree86-VidModeExtension
[ 45267.077] (II) Loading extension XFree86-DGA
[ 45267.077] (II) Loading extension DPMS
[ 45267.077] (II) Loading extension XVideo
[ 45267.077] (II) Loading extension XVideo-MotionCompensation
[ 45267.077] (II) Loading extension X-Resource
[ 45267.077] (II) LoadModule: "glx"
[ 45267.077] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 45267.092] (II) Module glx: vendor="NVIDIA Corporation"
[ 45267.092] compiled for 4.0.2, module version = 1.0.0
[ 45267.092] Module class: X.Org Server Extension
[ 45267.092] (II) NVIDIA GLX Module 270.41.19 Mon May 16 23:48:30 PDT 2011
[ 45267.092] (II) Loading extension GLX
[ 45267.092] (II) LoadModule: "record"
[ 45267.092] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 45267.092] (II) Module record: vendor="X.Org Foundation"
[ 45267.092] compiled for 1.10.1, module version = 1.13.0
[ 45267.092] Module class: X.Org Server Extension
[ 45267.092] ABI class: X.Org Server Extension, version 5.0
[ 45267.092] (II) Loading extension RECORD
[ 45267.092] (II) LoadModule: "dri"
[ 45267.092] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 45267.092] (II) Module dri: vendor="X.Org Foundation"
[ 45267.092] compiled for 1.10.1, module version = 1.0.0
[ 45267.092] ABI class: X.Org Server Extension, version 5.0
[ 45267.092] (II) Loading extension XFree86-DRI
[ 45267.092] (II) LoadModule: "dri2"
[ 45267.092] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 45267.092] (II) Module dri2: vendor="X.Org Foundation"
[ 45267.092] compiled for 1.10.1, module version = 1.2.0
[ 45267.092] ABI class: X.Org Server Extension, version 5.0
[ 45267.093] (II) Loading extension DRI2
[ 45267.093] (II) LoadModule: "nvidia"
[ 45267.093] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 45267.093] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 45267.093] compiled for 4.0.2, module version = 1.0.0
[ 45267.093] Module class: X.Org Video Driver
[ 45267.094] (II) NVIDIA dlloader X Driver 270.41.19 Mon May 16 23:33:35 PDT 2011
[ 45267.094] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 45267.094] (++) using VT number 8
[ 45267.096] (II) Loading sub module "fb"
[ 45267.096] (II) LoadModule: "fb"
[ 45267.096] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 45267.097] (II) Module fb: vendor="X.Org Foundation"
[ 45267.097] compiled for 1.10.1, module version = 1.0.0
[ 45267.097] ABI class: X.Org ANSI C Emulation, version 0.4
[ 45267.097] (II) Loading sub module "wfb"
[ 45267.097] (II) LoadModule: "wfb"
[ 45267.097] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 45267.097] (II) Module wfb: vendor="X.Org Foundation"
[ 45267.097] compiled for 1.10.1, module version = 1.0.0
[ 45267.097] ABI class: X.Org ANSI C Emulation, version 0.4
[ 45267.097] (II) Loading sub module "ramdac"
[ 45267.097] (II) LoadModule: "ramdac"
[ 45267.097] (II) Module "ramdac" already built-in
[ 45267.097] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 45267.097] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 45267.097] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 45267.097] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[ 45267.097] (==) NVIDIA(0): RGB weight 888
[ 45267.097] (==) NVIDIA(0): Default visual is TrueColor
[ 45267.097] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 45267.097] (**) NVIDIA(0): Option "DPI" "60x60"
[ 45267.369] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-0)) does not support NVIDIA
[ 45267.369] (II) NVIDIA(GPU-0): 3D Vision stereo.
[ 45267.370] (II) NVIDIA(0): NVIDIA GPU GeForce 8300 (C77) at PCI:2:0:0 (GPU-0)
[ 45267.370] (--) NVIDIA(0): Memory: 524288 kBytes
[ 45267.370] (--) NVIDIA(0): VideoBIOS: 62.77.2f.00.00
[ 45267.370] (--) NVIDIA(0): Interlaced video modes are supported on this GPU
[ 45267.370] (--) NVIDIA(0): Connected display device(s) on GeForce 8300 at PCI:2:0:0
[ 45267.370] (--) NVIDIA(0): Samsung SyncMaster (DFP-0)
[ 45267.370] (--) NVIDIA(0): Samsung SyncMaster (DFP-0): 165.0 MHz maximum pixel clock
[ 45267.370] (--) NVIDIA(0): Samsung SyncMaster (DFP-0): Internal Single Link TMDS
[ 45267.372] (WW) NVIDIA(0): The EDID for Samsung SyncMaster (DFP-0) contradicts itself:
[ 45267.372] (WW) NVIDIA(0): mode "720x480" is specified in the EDID; however, the
[ 45267.372] (WW) NVIDIA(0): EDID's valid HorizSync range (27.000-81.000 kHz) would
[ 45267.372] (WW) NVIDIA(0): exclude this mode's HorizSync (15.7 kHz); ignoring
[ 45267.372] (WW) NVIDIA(0): HorizSync check for mode "720x480".
[ 45267.372] (WW) NVIDIA(0): The EDID for Samsung SyncMaster (DFP-0) contradicts itself:
[ 45267.372] (WW) NVIDIA(0): mode "720x576" is specified in the EDID; however, the
[ 45267.372] (WW) NVIDIA(0): EDID's valid HorizSync range (27.000-81.000 kHz) would
[ 45267.372] (WW) NVIDIA(0): exclude this mode's HorizSync (15.6 kHz); ignoring
[ 45267.372] (WW) NVIDIA(0): HorizSync check for mode "720x576".
[ 45267.375] (WW) NVIDIA(0): The EDID for Samsung SyncMaster (DFP-0) contradicts itself:
[ 45267.375] (WW) NVIDIA(0): mode "720x480" is specified in the EDID; however, the
[ 45267.375] (WW) NVIDIA(0): EDID's valid HorizSync range (27.000-81.000 kHz) would
[ 45267.375] (WW) NVIDIA(0): exclude this mode's HorizSync (15.7 kHz); ignoring
[ 45267.375] (WW) NVIDIA(0): HorizSync check for mode "720x480".
[ 45267.376] (WW) NVIDIA(0): The EDID for Samsung SyncMaster (DFP-0) contradicts itself:
[ 45267.376] (WW) NVIDIA(0): mode "720x576" is specified in the EDID; however, the
[ 45267.376] (WW) NVIDIA(0): EDID's valid HorizSync range (27.000-81.000 kHz) would
[ 45267.376] (WW) NVIDIA(0): exclude this mode's HorizSync (15.6 kHz); ignoring
[ 45267.376] (WW) NVIDIA(0): HorizSync check for mode "720x576".
[ 45267.402] (II) NVIDIA(0): Assigned Display Device: DFP-0
[ 45267.402] (==) NVIDIA(0):
[ 45267.402] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[ 45267.402] (==) NVIDIA(0): will be used as the requested mode.
[ 45267.402] (==) NVIDIA(0):
[ 45267.402] (II) NVIDIA(0): Validated modes:
[ 45267.402] (II) NVIDIA(0): "nvidia-auto-select"
[ 45267.402] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[ 45267.426] (**) NVIDIA(0): DPI set to (60, 60); computed from "DPI" X config option
[ 45267.426] (--) Depth 24 pixmap format is 32 bpp
[ 45267.426] (II) NVIDIA: Using 768.00 MB of virtual memory for indirect memory access.
[ 45267.430] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 45267.430] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 45267.430] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 45267.430] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 45267.430] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 45267.430] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 45267.430] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 45267.430] (II) NVIDIA(0): Config Options in the README.
[ 45267.431] (II) NVIDIA(0): Setting mode "nvidia-auto-select"
[ 45267.472] (II) Loading extension NV-GLX
[ 45267.508] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 45267.508] (==) NVIDIA(0): Backing store disabled
[ 45267.508] (==) NVIDIA(0): Silken mouse enabled
[ 45267.509] (**) NVIDIA(0): DPMS enabled
[ 45267.509] (II) Loading extension NV-CONTROL
[ 45267.510] (II) Loading extension XINERAMA
[ 45267.510] (II) Loading sub module "dri2"
[ 45267.510] (II) LoadModule: "dri2"
[ 45267.510] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 45267.510] (II) Module dri2: vendor="X.Org Foundation"
[ 45267.510] compiled for 1.10.1, module version = 1.2.0
[ 45267.510] ABI class: X.Org Server Extension, version 5.0
[ 45267.510] (II) NVIDIA(0): [DRI2] Setup complete
[ 45267.510] (==) RandR enabled
[ 45267.510] (II) Initializing built-in extension Generic Event Extension
[ 45267.510] (II) Initializing built-in extension SHAPE
[ 45267.510] (II) Initializing built-in extension MIT-SHM
[ 45267.510] (II) Initializing built-in extension XInputExtension
[ 45267.510] (II) Initializing built-in extension XTEST
[ 45267.510] (II) Initializing built-in extension BIG-REQUESTS
[ 45267.510] (II) Initializing built-in extension SYNC
[ 45267.510] (II) Initializing built-in extension XKEYBOARD
[ 45267.510] (II) Initializing built-in extension XC-MISC
[ 45267.510] (II) Initializing built-in extension SECURITY
[ 45267.510] (II) Initializing built-in extension XINERAMA
[ 45267.510] (II) Initializing built-in extension XFIXES
[ 45267.510] (II) Initializing built-in extension RENDER
[ 45267.510] (II) Initializing built-in extension RANDR
[ 45267.510] (II) Initializing built-in extension COMPOSITE
[ 45267.510] (II) Initializing built-in extension DAMAGE
[ 45267.512] (II) Initializing extension GLX
[ 45267.586] (II) config/udev: Adding input device Power Button (/dev/input/event3)
[ 45267.586] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 45267.586] (II) LoadModule: "evdev"
[ 45267.586] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 45267.586] (II) Module evdev: vendor="X.Org Foundation"
[ 45267.586] compiled for 1.10.0, module version = 2.6.0
[ 45267.586] Module class: X.Org XInput Driver
[ 45267.586] ABI class: X.Org XInput driver, version 12.2
[ 45267.586] (II) Using input driver 'evdev' for 'Power Button'
[ 45267.586] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 45267.586] (**) Power Button: always reports core events
[ 45267.586] (**) Power Button: Device: "/dev/input/event3"
[ 45267.605] (--) Power Button: Found keys
[ 45267.605] (II) Power Button: Configuring as keyboard
[ 45267.605] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event3"
[ 45267.605] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
[ 45267.605] (**) Option "xkb_rules" "evdev"
[ 45267.605] (**) Option "xkb_model" "evdev"
[ 45267.605] (**) Option "xkb_layout" "se"
[ 45267.636] (II) config/udev: Adding input device Video Bus (/dev/input/event1)
[ 45267.636] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 45267.636] (II) Using input driver 'evdev' for 'Video Bus'
[ 45267.636] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 45267.636] (**) Video Bus: always reports core events
[ 45267.636] (**) Video Bus: Device: "/dev/input/event1"
[ 45267.648] (--) Video Bus: Found keys
[ 45267.648] (II) Video Bus: Configuring as keyboard
[ 45267.648] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A03:00/device:12/LNXVIDEO:00/input/input1/event1"
[ 45267.648] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD)
[ 45267.648] (**) Option "xkb_rules" "evdev"
[ 45267.648] (**) Option "xkb_model" "evdev"
[ 45267.648] (**) Option "xkb_layout" "se"
[ 45267.650] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[ 45267.650] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 45267.650] (II) Using input driver 'evdev' for 'Power Button'
[ 45267.650] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 45267.650] (**) Power Button: always reports core events
[ 45267.650] (**) Power Button: Device: "/dev/input/event2"
[ 45267.662] (--) Power Button: Found keys
[ 45267.662] (II) Power Button: Configuring as keyboard
[ 45267.662] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input2/event2"
[ 45267.662] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
[ 45267.662] (**) Option "xkb_rules" "evdev"
[ 45267.662] (**) Option "xkb_model" "evdev"
[ 45267.662] (**) Option "xkb_layout" "se"
[ 45267.666] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event5)
[ 45267.666] (**) Logitech USB Receiver: Applying InputClass "evdev keyboard catchall"
[ 45267.666] (II) Using input driver 'evdev' for 'Logitech USB Receiver'
[ 45267.666] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 45267.666] (**) Logitech USB Receiver: always reports core events
[ 45267.666] (**) Logitech USB Receiver: Device: "/dev/input/event5"
[ 45267.675] (--) Logitech USB Receiver: Found keys
[ 45267.675] (II) Logitech USB Receiver: Configuring as keyboard
[ 45267.675] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:04.0/usb4/4-3/4-3:1.0/input/input5/event5"
[ 45267.675] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD)
[ 45267.675] (**) Option "xkb_rules" "evdev"
[ 45267.675] (**) Option "xkb_model" "evdev"
[ 45267.675] (**) Option "xkb_layout" "se"
[ 45267.676] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event6)
[ 45267.676] (**) Logitech USB Receiver: Applying InputClass "evdev pointer catchall"
[ 45267.676] (**) Logitech USB Receiver: Applying InputClass "evdev keyboard catchall"
[ 45267.676] (II) Using input driver 'evdev' for 'Logitech USB Receiver'
[ 45267.676] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 45267.676] (**) Logitech USB Receiver: always reports core events
[ 45267.676] (**) Logitech USB Receiver: Device: "/dev/input/event6"
[ 45267.685] (--) Logitech USB Receiver: Found 12 mouse buttons
[ 45267.685] (--) Logitech USB Receiver: Found scroll wheel(s)
[ 45267.685] (--) Logitech USB Receiver: Found relative axes
[ 45267.685] (--) Logitech USB Receiver: Found x and y relative axes
[ 45267.685] (--) Logitech USB Receiver: Found absolute axes
[ 45267.685] (--) Logitech USB Receiver: Found keys
[ 45267.685] (II) Logitech USB Receiver: Configuring as mouse
[ 45267.685] (II) Logitech USB Receiver: Configuring as keyboard
[ 45267.685] (II) Logitech USB Receiver: Adding scrollwheel support
[ 45267.685] (**) Logitech USB Receiver: YAxisMapping: buttons 4 and 5
[ 45267.685] (**) Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 45267.685] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:04.0/usb4/4-3/4-3:1.1/input/input6/event6"
[ 45267.685] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD)
[ 45267.685] (**) Option "xkb_rules" "evdev"
[ 45267.685] (**) Option "xkb_model" "evdev"
[ 45267.685] (**) Option "xkb_layout" "se"
[ 45267.685] (II) Logitech USB Receiver: initialized for relative axes.
[ 45267.685] (WW) Logitech USB Receiver: ignoring absolute axes.
[ 45267.686] (**) Logitech USB Receiver: (accel) keeping acceleration scheme 1
[ 45267.686] (**) Logitech USB Receiver: (accel) acceleration profile 0
[ 45267.686] (**) Logitech USB Receiver: (accel) acceleration factor: 2.000
[ 45267.686] (**) Logitech USB Receiver: (accel) acceleration threshold: 4
[ 45267.686] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/mouse0)
[ 45267.686] (II) No input driver/identifier specified (ignoring)
[ 45267.687] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event4)
[ 45267.687] (II) No input driver/identifier specified (ignoring)
[ 45267.692] (II) config/udev: Adding input device PC Speaker (/dev/input/event0)
[ 45267.692] (II) No input driver/identifier specified (ignoring)

I seem to have been unclear in my original post. Setting it in Gnome 3 would all be fine and dandy, however although Gnome 3 was installed (upgraded from 2.x), I use fvwm. Gtk etc is still used but I don't see why upgrading a DE I don't use would impair another WM from using the X11 DPI settings. Also changing that setting in Gnome 3 does not affect neither the login screen (GDM) nor anything in fvwm.

Cannot send email from Iphone. A setting is off.

What are the correct settings to send email from my aol account that's included in my I Cloud acct. any suggestions???? Thanks Sue

Read this
How do I set up AOL Mail on my iPhone or iPod Touch? - AOL Help

HOW TO SET UP PARTNER APPLICATION TO USE SSO OUTSIDE OF PORTAL

If anyone knows how Portal switches context to run as the db user mapped to the lightweight schema and how it knows the db schema password please let me know.
Should you have any queries please do not hesitate to contact me on 07775 896738.
From document Oracle Portal Security Overview on PortalStudio.oracle.com:
In Single Sign On mode (EnableSSO=Yes in the DAD), mod_plsql determines the name of the light-weight user and mapped database schema by calling
WPG_SESSION_PRIVATE.GET_LW_USER and WPG_SESSION_PRIVATE.GET_DB_USER respectively.
** These calls are done using the Portal Schema (PORTAL30) and Portal schema password **
mod_plsql then executes the procedure in the requested URL by using the N-Tier Authentication feature to connect to the database as the user returned from
WPG_SESSION_PRIVATE.GET_DB_USER. ..... Note that N-Tier Authentication requires all schemas to be used for Portal user mappings to be granted 'connect
through' privleges to the Portal schema (PORTAL30).
The WWCTX packages are also used.
So this is how it works with standard Portal
- the document states that the WPG_SESSION_PRIVATE package is only accessible to the Portal schema
- but I checked and it is also available to PORTAL30_SSO
SQL> desc WPG_SESSION_PRIVATE
PROCEDURE CREATE_SESSION
Argument Name Type In/Out Default?
P_COOKIE_NAME VARCHAR2 IN
FUNCTION GET_DB_USER RETURNS VARCHAR2
FUNCTION GET_LW_USER RETURNS VARCHAR2
PROCEDURE GET_SESSION_INFO
Argument Name Type In/Out Default?
NUM_PARAMS NUMBER OUT
PARAM_NAMES TABLE OF VARCHAR2(32000) OUT
PARAM_VALUES TABLE OF VARCHAR2(32000) OUT
PROCEDURE RESET_SESSION
Argument Name Type In/Out Default?
P_COOKIE_NAME VARCHAR2 IN
In my case only the Login Server (PORTAL30_SSO) is going to be used/installed
- the SAMPLE_SSO_PAPP application will only work if the DAD used to access is it set to use Basic authentication, i.e. the actual integration with the Login Server
is done in the sample application code calls, stored in the database
- when a DAD has enableSSO=yes it automatically accesses Portal (PORTAL30) packages to implement N-Tier authentication
I'm currently testing:
1. Configuring the SAMPLE_SSO_PAPP sample as documented with a DAD with Basic authentication
2. Amending the ssoapp procedure to set context to another (db) user on successful authentication:
wwctx_api.set_context (
p_user_name => 'SCOTT',
p_password => 'TIGER' );
3. If this works then set_context with get_lw_user instead
I have now amended the ssoapp procedure as follows to print out
1. The userid entered when the login box is presented
2. The Database user which the Portal Lightweight user is mapped to
3. The Lightweight user Portal has used for authentication
Amendments to papp.pkb:
(ssoapp procedure, declare db_user_info and lw_user_info as VARCHAR2 in declare section)
htp.p('Congratulations! It is working!<br>');
db_user_info := wwctx_api.get_db_user;
lw_user_info := wwctx_api.get_user;
htp.p('User Information:' || l_user_info || '<br>');
htp.p('DB User Information:' || db_user_info || '<br>');
htp.p('LW User Information:' || lw_user_info || '<br>');
The following shows the interesting results from my testing:
- if the user owning the sample_sso_papp package is PORTAL30_SSO then the call to wwctx_api.get_db_user succeeds
- if the user owning the sample_sso_papp package is a non-portal schema e.g. SSOAPP below the call to wwctx_api.get_db_user generates a User Defined exception
Steps to test:
Created new schema SSOAPP on the database
- edited it in Portal and checked the use this schema for Portal users checkbox
- created new Lightweight user SSO_LW in Portal, mapped it to SSOAPP schema
- created new Lightweight user SSO_SCOTT in Portal, mapped to SCOTT schema
- loadjava -user ssoapp/ssoapp@portal30 SSOHash.class
- sqlplus portal30/portal30@portal30
@provsyns ssoapp
- sqlplus ssoapp/ssoapp@portal30
@loadsdk.sql
@loadpapp.sql
Created DAD with basic authentication SAMPLE_SSO_PAPP
- username: ssoapp
- default home page: sample_sso_papp.ssoapp
Registered the Sample SSO Partner Application with the Login Server and ran regapp.sql
Commented out the calls to get_db_user in papp.pkb to avoid exception
- called http://<server>/pls/sample_sso_papp
- logged on as SSO_LW/sso_lw
- got output:
Congratulations! It is working!
User Information: SSO_LW
LW User Information: PUBLIC
So the Portal lightweight user is not returned as SSO_LW
if anyone knows why the Lightweight User in my test is returned as PUBLIC not SSO_LW
Best Regards
MIchael

http://support.mozilla.com/en-US/kb/Changing+the+e-mail+program+used+by+Firefox

Battery , time , signal strength bar is not getting displayed in home screen , these will be displayed only when i click on any app. Can u let me know the setting change ?

Battery , time , signal strength bar is not getting displayed in home screen , these will be displayed only when i click on any app. Can u let me know the setting change ?

Did you check the Zoom setting?
Have you tried a reset (reboot)? Hold HOME and SLEEP until an Apple logo appears.
If it isn't Zoom and a reboot doesn't help try Settings/General/Reset - Reset all settings

Set-up of DRP

Similar Messages

Maybe you are looking for