PO Output triggerd twice with wrong partner

Hi All,
I am facing a issue with PO Output as below:
I have PO output as EDI as well as External Send, EDI is triggered thru a batch job, and immediately system has triggerred exteral send as output to partner VN , who is different than in PO. For e.g. in PO VN is ABC, where as in external send it has taken XYZ.
I have checked in PO for the partner determination, there is no other partner function other than VN and ABC vendor name is shown there.
This has resulted into PO emailed to wrong Vendor.
Can anyone help me to find out the reason ?
Thanks & Regards,
Vikas

It seems incorrect partner is assigned to the message type .Please check in spro configuration.
SPRO>Materials Management>Purchasing>Messages>Output Control>Partner Roles per Message Type>Define Partner Roles for Purchase Order.
IFor external send it should have incorrect partner.

Similar Messages

Wrong Partner Type in IDoc with message type REMADV

Dear all,
We have created 2 IDocs, one for outbound (first in one company code) and one for inbound (receiving company code) with transaction F110 (message type REMADV, Idoc basic type PEXR2001). However, for the first outbound IDoc we have created, we have the wrong Partner type (we would like it to get type KU (customer)) LS (Logic system).
Does anyone know how to change the partner type from the Idoc generationg?
Many thanks,
Ronny

Hi,
Welcome to SDN.
Please delete the exisiting outbound partner profile (WE20) for message type REMADV which under partner type LS (Logical System) and setup new outbound partner profile for partner type KU (Customer).
Regards,
Ferry Lianto

Message "Wrong partner type LS" in message control

Hi All,
I am trying to send PO's out to a middleware system. I have configured the middleware system as a LS (logical system) done all the config required for Message control.
But when I enter Output type = NEU and Medium = A (ALE) and Partner Function = LS and partner name and save the PO, I get the error "Wrong Partner type LS" in the processing log for that message. The details description says "The message record of the message control contains a partner role with a partner type LS that cannot be used here. Only the 'KU' and 'LI' partner types are allowed.". But i need to send it to partner type LS.
Am I missing anything. Please Advise.
Thanks in advance

Hi!
'By default' purchase orders can be send to vendors or plants - the two parties in the document. This is linked to the two different partner types KU and LI. Only partners of this type of a purchase order can be used to send data.
Check, if you can create a partner definition (WE20) for KU (hopefully you have less plants then vendors).
You also need a partner determination for the document - only out of this partners automatically a message output can be assigned.
Regards,
Christian

Error Wrong partner type LS

Hi All,
I am doing IDOC to File Scenario where i am sending Purchase order details to third party system. When i create or change the PO it should generate ORDER05 idoc and send to PI. I configured output type to generate PO idoc but it is not generating idoc. Configured details is as below
Output type :NEU
In General tab:Access to conditions and multiple issuing is checked
Default value
Dispatch time: Send immediately
Transmission medium: Distribution ALE
Partner function: LS
Processing routines: Distribution( ALE ) RSNASTED ALE_PROCESSING
Partner function:Distribution( ALE ) LS Logical System
Procedure: RMBEF1 Purchase Order.
I activated this procedure in SPRO Tcode
In condition record
I choosen purchase org option and gave the following details.
Pur Org: RS00
Function: LS
Partner: XXXXX001
Medium :A
Date: 4
I did configuration in partner profile by adding orders details and message control details in in XXXXX001. I also configured Distribution model.
When i create PO the above mentioned condition records are coming in the message type. when i check process log in me22 it says Wrong partner type LS The message record of the message control contains a partner role with a partner type LS that cannot be used here. Only the 'KU' and 'LI' partner types are allowed
i used this as reference
www saptechnical com/Tutorials/ALE/AutoIDOCGen/AutomaticIDocGeneration2.htm
I have searched entire SDN form no one has given correct answer. Please let me know what is the problem.
Thanks,
Venky

Hi venkatesh,
Here are the details of the ALE configuration for sending the IDOCS to FILE.
SAP:
1. RFC destination to XI system.
2. Check the message type.
3. create the logical system ( hope this is created if you are working in any projects )
as this is a one time activity and is done by the basis team at the time of post installation process.
LS ---> SAP
LS1--->XI
3. define a port to send the IDOCS.
4. go to WE 20. create a partner profile. and provide the message type in the outbound parameters.
and provide the port details.
5. Create a CDM(BD64) and provide the details.
XI:
1. Create an RFC connection to SAP system.
2. Define the port details from IDX1
3. upload the meta data from IDX2.
go to WE19 and generate the IDOCS and see if the IDocs are sucessfully send to the port or not from WE02.
Check in XI side if the IDocs hits or not.
Thanks,
Jay

Issue with trading partner

Hi ,
I have a issue with trading partner,
While clearing the bank clearing account with bank main account user has got the below error
"Consolidated companies ' ' are different"
The issue is because u201CTrading Partneru201D, document number xxxx has the trading partner.
I have given the below solution to client,
Proposed solution:
Reverse the payment & invoice documents
Edit the vendor master data (Remove the trading partner from vendor master data)
Re-post the invoice
Do the payment document
Now client does not want to revere the document, do we have any other way to do this?
Regards,
Sridhar

Hi Sridhar,
if you make wrong entry in VBUND, it is necessary to REVERSE the document first and re-post with the correct VBUND information. BSEG-VBUND is one of the important organizational fields which should be managed in the same manner as company code, business area etc. These organizational fields cannot/should not be changed.
Please refer to note 4152, which provides valuable information on why
the error F5080 arises in your system.
Also please consider the following points:
There is also another note, 109925, which describes in detail the
possibility to transfer, into all the line items, the trading partner.
Use
o If you want the trading partner to be transferred to all line items,
do NOT set this indicator.
The System behaviour is the following one:
1) Both indicators switched OFF:
If a trading partner is maintained in G/L, vendor or customer master
record, VBUND is copied to all document lines. VBUND is unique
in FI-document.
2) Indicator "Multiple companies" switched ON and indicator
"Enter trading partner" switched OFF:
The company ID (= trading partner) is not inherited to other items for
document types that allow cross-company postings.
3) Indicator "Multiple companies" switched ON and indicator
"Enter trading partner" switched ON:
You can enter a trading partner when posting to a G/L account and in
the G/L master record, no trading partner is stored.
In this case, the company ID specified manually is entered in all
line items that not yet received a company code from the customer
or vendor master record.
Kind Regards,
Mateus

Output type maintained for same partner function.

Hi Gurus,
Can we maintain outupt type for different transmission medium like print output, EDI and special function with in same partner function ? Please explain also?
Thanks in advance.
Regards
Hemat ghiya
Edited by: Hemant ghiya on Oct 5, 2011 1:28 PM

Hi Rags,
Thanks for your quick reply but i am getting problem at the time of determination . Once i have determined for one medium and then i will determine for another medium with same partner function then it is giving error like this partner funcition alerady used.
So i am not able to determined for the another transmission medium after determining for one medium.
Can you give your valueable suggestion.
Thanks in advance.
Regards
Hemant ghiya

Maintain same customer number twice with different GUIDs

Recently, R3 refreshed, but CRM not. After refresh R3 is having few customer & product numbers, which were same as earlier. That means those customers & products already exist in CRM. I run initial load for customizing & master data from R3 to CRM.
Now, I can see existing product number can be downloaded from R3 & result is same product number present twice in CRM with different GUIDs.
For customer, I am not able to download existing customer number via initial load. I am getting mapping error & error description - "Customer number EKC3137 is already assigned to a business partner". Delta load also failed for same customer with error - "Business partner with GUID 15ECAD322FDA074BB8B125DEDB4194DB does not exist". I checked & found existing entry in CRM is having different GUID for this customer.
Can anyone suggest how to download this customer with new GUID, keeping same customer with different GUID. This means expected result is same customer number maintained twice with two different GUIDs. Definitely old customer can not be updated from R3, but new one can be updated in future.
Regards,
Soumya

Hi.
Everytime you do a not simultaneous client copy you will get this inconsistencies on middleware data.
You can correct this as described below:
CUSTOMERS:
Apply note 609766 in order to create a report that will correct the customers Guids on tables: R/3: CRMKUNNR and CRM: CRMM_BUT_CUSTNO .
MATERIAL:
R/3 table that contains CRM product guid: NDBSMATG16
CRM table: COMM_PRODUCT
SAP recomends to delete all products and replicate them again: COM_PRODUCT_DELETE_SINGLE
Possible problem if you also have price condition tables on CRM (the product Guids will be the old ones so yoiu will have to download all pricing data again).
CONTACT PERSONS:
R/3: CRMPARNR
CRM: CRMM_BUT_CONTNO
Apply note 703322 and run report Z_OSS_000400_2004 on R/3 and corrects the inconsistencies.
Regards.
Susana Messias

Systemd device dev-disk-by\{stuff} appeared twice with sysfs diff path

$ dmesg -l err
[ 6.330201] systemd[1]: Device dev-disk-by\x2duuid-d527fcab\x2d1897\x2d46a1\x2d8324\x2d18de507f4993.device appeared twice with different sysfs paths /sys/devices/virtual/block/bcache0 and /sys/devices/virtual/block/bcache2
[ 6.332384] systemd[1]: Device dev-disk-by\x2dlabel-raid0.device appeared twice with different sysfs paths /sys/devices/virtual/block/bcache2 and /sys/devices/virtual/block/bcache1
[ 6.334041] systemd[1]: Device dev-disk-by\x2duuid-d527fcab\x2d1897\x2d46a1\x2d8324\x2d18de507f4993.device appeared twice with different sysfs paths /sys/devices/virtual/block/bcache0 and /sys/devices/virtual/block/bcache1
[ 6.730564] systemd[1]: Device dev-disk-by\x2dlabel-raid0.device appeared twice with different sysfs paths /sys/devices/virtual/block/bcache2 and /sys/devices/virtual/block/bcache3
[ 6.732213] systemd[1]: Device dev-disk-by\x2duuid-d527fcab\x2d1897\x2d46a1\x2d8324\x2d18de507f4993.device appeared twice with different sysfs paths /sys/devices/virtual/block/bcache0 and /sys/devices/virtual/block/bcache3
[ 6.997304] systemd[1]: Device dev-disk-by\x2dlabel-jabod.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc3 and /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf3
[ 6.999960] systemd[1]: Device dev-disk-by\x2duuid-0d19cfc3\x2d7588\x2d4c19\x2db85e\x2dbf3a3db2d4a0.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc3 and /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf3
[ 7.003235] systemd[1]: Device dev-disk-by\x2dlabel-raid1.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc2 and /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf1
[ 7.005881] systemd[1]: Device dev-disk-by\x2duuid-99fd7889\x2dde7a\x2d4b30\x2d9745\x2d8ccb2b1ee75d.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc2 and /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf1
[ 7.194594] systemd[1]: Device dev-disk-by\x2dlabel-aroot.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf4 and /sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/ata7/host6/target6:0:0/6:0:0:0/block/sde/sde1
[ 7.197369] systemd[1]: Device dev-disk-by\x2duuid-3873d8ba\x2d9472\x2d4d92\x2dab0d\x2de94574bd0eae.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf4 and /sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/ata7/host6/target6:0:0/6:0:0:0/block/sde/sde1
[ 7.207859] systemd[1]: Device dev-disk-by\x2dlabel-raid1.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc2 and /sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/ata7/host6/target6:0:0/6:0:0:0/block/sde/sde3
[ 7.210477] systemd[1]: Device dev-disk-by\x2duuid-99fd7889\x2dde7a\x2d4b30\x2d9745\x2d8ccb2b1ee75d.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc2 and /sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/ata7/host6/target6:0:0/6:0:0:0/block/sde/sde3
[ 7.240459] systemd[1]: Device dev-disk-by\x2dlabel-aroot.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf4 and /sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb2
[ 7.243114] systemd[1]: Device dev-disk-by\x2duuid-3873d8ba\x2d9472\x2d4d92\x2dab0d\x2de94574bd0eae.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf4 and /sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb2
[ 8.062829] systemd[1]: Device dev-disk-by\x2dlabel-jabod.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc3 and /sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb4
[ 8.065328] systemd[1]: Device dev-disk-by\x2duuid-0d19cfc3\x2d7588\x2d4c19\x2db85e\x2dbf3a3db2d4a0.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc3 and /sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb4
I've been getting this since I upgraded systemd last week. I tried fixing some of these by removing partitions with the same label that I wasn't using, which worked. The reason I have so many partitions with the same label is due to btrfs. Each partition that makes up a volume in btrfs has the same label. Apparently systemd doesn't like this.
Everything on my system seems to be working fine, however I would like to stop these errors since they are annoying/scary, but without having to reduce all my volumes to single.
Last edited by nstgc (2015-04-26 15:53:20)

I'm running with a wired-only set up. I'll have to wait for the weekend to look into the wireless angle, however I doubt that is the cause for me.
Following dront78's example below is the output of "# hwinfo --partitions"
75: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: bdUI.SE1wIdpsiiC
Parent ID: 3OOL.7ppt9e3ai+9
SysFS ID: /class/block/sda/sda1
Hardware Class: partition
Model: "Partition"
Device File: /dev/sda1
Device Files: /dev/sda1, /dev/disk/by-id/ata-KINGSTON_SH103S3240G_50026B7234025EC8-part1, /dev/disk/by-id/wwn-0x6829766019904589826x-part1, /dev/disk/by-partuuid/77f1354c-3b20-454d-ba60-9dbab9bc8640, /dev/disk/by-uuid/ff387510-d0ad-498f-8d1b-576b26ed103e
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #74 (Disk)
76: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: 2pkM.SE1wIdpsiiC
Parent ID: 3OOL.7ppt9e3ai+9
SysFS ID: /class/block/sda/sda2
Hardware Class: partition
Model: "Partition"
Device File: /dev/sda2
Device Files: /dev/sda2, /dev/disk/by-id/ata-KINGSTON_SH103S3240G_50026B7234025EC8-part2, /dev/disk/by-id/wwn-0x6829766019904589826x-part2, /dev/disk/by-partuuid/44596381-4cfe-4a2d-8e7b-f6427cc089d0
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #74 (Disk)
77: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: W__Q.SE1wIdpsiiC
Parent ID: 3OOL.7ppt9e3ai+9
SysFS ID: /class/block/sda/sda3
Hardware Class: partition
Model: "Partition"
Device File: /dev/sda3
Device Files: /dev/sda3, /dev/disk/by-id/ata-KINGSTON_SH103S3240G_50026B7234025EC8-part3, /dev/disk/by-id/wwn-0x6829766019904589826x-part3, /dev/disk/by-partuuid/c9b404ec-f407-4081-a69c-9b10360d4cf7
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #74 (Disk)
78: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: z9FV.SE1wIdpsiiC
Parent ID: 3OOL.7ppt9e3ai+9
SysFS ID: /class/block/sda/sda4
Hardware Class: partition
Model: "Partition"
Device File: /dev/sda4
Device Files: /dev/sda4, /dev/disk/by-id/ata-KINGSTON_SH103S3240G_50026B7234025EC8-part4, /dev/disk/by-id/wwn-0x6829766019904589826x-part4, /dev/disk/by-partuuid/69c0972d-51ed-429c-acea-6e1afd7ebb1f
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #74 (Disk)
80: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: h4pj.SE1wIdpsiiC
Parent ID: WZeP.bTSLTpVNGx8
SysFS ID: /class/block/sdb/sdb1
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdb1
Device Files: /dev/sdb1, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33388736-part1, /dev/disk/by-id/wwn-0x17950130428369588225x-part1, /dev/disk/by-uuid/2c0f1039-2d4b-4f75-8fa4-529d19cd18fc
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #79 (Disk)
81: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: 8G3o.SE1wIdpsiiC
Parent ID: WZeP.bTSLTpVNGx8
SysFS ID: /class/block/sdb/sdb2
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdb2
Device Files: /dev/sdb2, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33388736-part2, /dev/disk/by-id/wwn-0x17950130428369588225x-part2, /dev/disk/by-label/aroot, /dev/disk/by-uuid/3873d8ba-9472-4d92-ab0d-e94574bd0eae
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #79 (Disk)
82: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: bRJs.SE1wIdpsiiC
Parent ID: WZeP.bTSLTpVNGx8
SysFS ID: /class/block/sdb/sdb3
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdb3
Device Files: /dev/sdb3, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33388736-part3, /dev/disk/by-id/wwn-0x17950130428369588225x-part3, /dev/disk/by-label/old-raid1, /dev/disk/by-uuid/dfa989d8-edac-4c7e-b6fc-45237e6a0ebc
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #79 (Disk)
83: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: 2dZw.SE1wIdpsiiC
Parent ID: WZeP.bTSLTpVNGx8
SysFS ID: /class/block/sdb/sdb4
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdb4
Device Files: /dev/sdb4, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33388736-part4, /dev/disk/by-id/wwn-0x17950130428369588225x-part4, /dev/disk/by-label/jabod, /dev/disk/by-uuid/0d19cfc3-7588-4c19-b85e-bf3a3db2d4a0
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #79 (Disk)
85: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: mX79.SE1wIdpsiiC
Parent ID: _kuT.rgQvtxWxfg6
SysFS ID: /class/block/sdc/sdc1
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdc1
Device Files: /dev/sdc1, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WMAW31235179-part1, /dev/disk/by-id/wwn-0x4611505914592251905x-part1, /dev/disk/by-uuid/80780835-de4b-462c-b7f0-2b389d3e2c2f
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #84 (Disk)
86: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: DjND.SE1wIdpsiiC
Parent ID: _kuT.rgQvtxWxfg6
SysFS ID: /class/block/sdc/sdc2
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdc2
Device Files: /dev/sdc2, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WMAW31235179-part2, /dev/disk/by-id/wwn-0x4611505914592251905x-part2, /dev/disk/by-label/raid1, /dev/disk/by-uuid/99fd7889-de7a-4b30-9745-8ccb2b1ee75d
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #84 (Disk)
87: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: gudH.SE1wIdpsiiC
Parent ID: _kuT.rgQvtxWxfg6
SysFS ID: /class/block/sdc/sdc3
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdc3
Device Files: /dev/sdc3, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WMAW31235179-part3, /dev/disk/by-id/wwn-0x4611505914592251905x-part3, /dev/disk/by-label/jabod, /dev/disk/by-uuid/0d19cfc3-7588-4c19-b85e-bf3a3db2d4a0
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #84 (Disk)
88: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: 74uL.SE1wIdpsiiC
Parent ID: _kuT.rgQvtxWxfg6
SysFS ID: /class/block/sdc/sdc4
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdc4
Device Files: /dev/sdc4, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WMAW31235179-part4, /dev/disk/by-id/wwn-0x4611505914592251905x-part4, /dev/disk/by-label/old-aroot, /dev/disk/by-uuid/b396dd50-e3f1-4b74-8cac-7d8d79a75386
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #84 (Disk)
90: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: r_Ra.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd1
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd1
Device Files: /dev/sdd1, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part1, /dev/disk/by-id/wwn-0x14865109125905272832x-part1, /dev/disk/by-partlabel/Microsoft\x20reserved\x20partition, /dev/disk/by-partuuid/f3e9ce24-988d-40ef-bd5c-6313c808bef2
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
91: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: IAie.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd2
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd2
Device Files: /dev/sdd2, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part2, /dev/disk/by-id/wwn-0x14865109125905272832x-part2, /dev/disk/by-partlabel/Basic\x20data\x20partition, /dev/disk/by-partuuid/f3344931-99c3-11e4-8601-806e6f6e6963, /dev/disk/by-uuid/30F403F0F403B75E
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
92: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: lLyi.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd3
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd3
Device Files: /dev/sdd3, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part3, /dev/disk/by-id/wwn-0x14865109125905272832x-part3, /dev/disk/by-partlabel/EFI\x20system\x20partition, /dev/disk/by-partuuid/ffbaa0cc-99c7-11e4-8625-806e6f6e6963, /dev/disk/by-uuid/0DE5-0CB0
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
93: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: CXCn.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd4
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd4
Device Files: /dev/sdd4, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part4, /dev/disk/by-id/wwn-0x14865109125905272832x-part4, /dev/disk/by-partlabel/Basic\x20data\x20partition, /dev/disk/by-partuuid/ffbaa0b6-99c7-11e4-8625-806e6f6e6963, /dev/disk/by-uuid/FE2648382647EFE7
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
94: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: fiSr.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd5
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd5
Device Files: /dev/sdd5, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part5, /dev/disk/by-id/wwn-0x14865109125905272832x-part5, /dev/disk/by-label/flbck, /dev/disk/by-partuuid/bd84f197-066e-4b9e-bf9b-b0b3a4090cde, /dev/disk/by-uuid/832bcc8d-836e-4b4e-8d9c-0a19f5bcf7dd
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
95: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: 6uiv.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd6
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd6
Device Files: /dev/sdd6, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part6, /dev/disk/by-id/wwn-0x14865109125905272832x-part6, /dev/disk/by-partuuid/8f77bc79-ba57-462e-8beb-d09db5c77490
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
96: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: oKuO.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd7
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd7
Device Files: /dev/sdd7, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part7, /dev/disk/by-id/wwn-0x14865109125905272832x-part7, /dev/disk/by-partuuid/7ca3eb27-d198-4915-9c71-e96fa7a34d8b, /dev/disk/by-uuid/fd43f1bd-9f52-41b7-badc-4ab7881473ee
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
97: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: GW8T.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd8
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd8
Device Files: /dev/sdd8, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part8, /dev/disk/by-id/wwn-0x14865109125905272832x-part8, /dev/disk/by-partuuid/550f9e19-c0ec-4474-9e98-84c727854158
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
98: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: cPdt.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd10
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd10
Device Files: /dev/sdd10, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part10, /dev/disk/by-id/wwn-0x14865109125905272832x-part10, /dev/disk/by-label/bckup, /dev/disk/by-partuuid/de7eaa1e-66b0-4058-ad71-d0f8ea470b2f, /dev/disk/by-uuid/723d7788-8514-4777-8e07-e0faa48c9a83
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
100: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: wRm+.SE1wIdpsiiC
Parent ID: u5Pc.jfv0tLKpnVA
SysFS ID: /class/block/sde/sde1
Hardware Class: partition
Model: "Partition"
Device File: /dev/sde1
Device Files: /dev/sde1, /dev/disk/by-id/ata-ST2000NM0053-1C1175_Z1X48TVG-part1, /dev/disk/by-id/wwn-0x9832618751734861824x-part1, /dev/disk/by-label/aroot, /dev/disk/by-uuid/3873d8ba-9472-4d92-ab0d-e94574bd0eae
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #99 (Disk)
101: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: Nd04.SE1wIdpsiiC
Parent ID: u5Pc.jfv0tLKpnVA
SysFS ID: /class/block/sde/sde2
Hardware Class: partition
Model: "Partition"
Device File: /dev/sde2
Device Files: /dev/sde2, /dev/disk/by-id/ata-ST2000NM0053-1C1175_Z1X48TVG-part2, /dev/disk/by-id/wwn-0x9832618751734861824x-part2, /dev/disk/by-uuid/aa19d2cf-e59d-4277-a5e6-d0078ede6d3b
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #99 (Disk)
102: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: qoG8.SE1wIdpsiiC
Parent ID: u5Pc.jfv0tLKpnVA
SysFS ID: /class/block/sde/sde3
Hardware Class: partition
Model: "Partition"
Device File: /dev/sde3
Device Files: /dev/sde3, /dev/disk/by-id/ata-ST2000NM0053-1C1175_Z1X48TVG-part3, /dev/disk/by-id/wwn-0x9832618751734861824x-part3, /dev/disk/by-label/raid1, /dev/disk/by-uuid/99fd7889-de7a-4b30-9745-8ccb2b1ee75d
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #99 (Disk)
103: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: H_WC.SE1wIdpsiiC
Parent ID: u5Pc.jfv0tLKpnVA
SysFS ID: /class/block/sde/sde4
Hardware Class: partition
Model: "Partition"
Device File: /dev/sde4
Device Files: /dev/sde4, /dev/disk/by-id/ata-ST2000NM0053-1C1175_Z1X48TVG-part4, /dev/disk/by-id/wwn-0x9832618751734861824x-part4
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #99 (Disk)
105: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: +u4R.SE1wIdpsiiC
Parent ID: LHfg.eZsVjjzwg10
SysFS ID: /class/block/sdf/sdf1
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdf1
Device Files: /dev/sdf1, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33509457-part1, /dev/disk/by-id/wwn-0x8355873293896667137x-part1, /dev/disk/by-label/raid1, /dev/disk/by-uuid/99fd7889-de7a-4b30-9745-8ccb2b1ee75d
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #104 (Disk)
106: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: S4LV.SE1wIdpsiiC
Parent ID: LHfg.eZsVjjzwg10
SysFS ID: /class/block/sdf/sdf2
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdf2
Device Files: /dev/sdf2, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33509457-part2, /dev/disk/by-id/wwn-0x8355873293896667137x-part2, /dev/disk/by-uuid/96fa47c5-061d-4849-8582-7186cc1695d2
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #104 (Disk)
107: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: vFbZ.SE1wIdpsiiC
Parent ID: LHfg.eZsVjjzwg10
SysFS ID: /class/block/sdf/sdf3
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdf3
Device Files: /dev/sdf3, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33509457-part3, /dev/disk/by-id/wwn-0x8355873293896667137x-part3, /dev/disk/by-label/jabod, /dev/disk/by-uuid/0d19cfc3-7588-4c19-b85e-bf3a3db2d4a0
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #104 (Disk)
108: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: NRrd.SE1wIdpsiiC
Parent ID: LHfg.eZsVjjzwg10
SysFS ID: /class/block/sdf/sdf4
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdf4
Device Files: /dev/sdf4, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33509457-part4, /dev/disk/by-id/wwn-0x8355873293896667137x-part4, /dev/disk/by-label/aroot, /dev/disk/by-uuid/3873d8ba-9472-4d92-ab0d-e94574bd0eae
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #104 (Disk)
i don't have time to look at this in detail this morning, but I will this afternoon.
Thank you for all the replies. Have any of you found this to actually be damaging?
[edit] In an effort to not be completely lazy, and because I was curious, I did check a bit into netctl. Running "$ netctl list" returned exactly nothing. I have no profiles.
[edit2]
I just ran "$ dmesg -l err" on my laptop and I'm not getting any errors.
Last edited by nstgc (2015-04-27 15:09:46)

Webi base on BW query based on Infoset comes back with wrong values

Hello:
I have a Webi report on an OLAP Universe, on Bex Query.
The bex query is based on 1 INFOSET.
When I run the webi report the values that comes back a totally wrong values.
The correct results are not brought back.
When I do a test with crystal reports to the infoset, I can see the correct values. (I'm aware crystal uses different drivers).
The test is BW query designer, and crystal brings back proper values from Infoset based BW query.
Webi on Infoset based BW Query comes back with wrong data.
query is simple.
Pull in 3 attributes, 3 key figures, where componentkey = "111"
I get 36 rows in Crystal and 36 rows in Bex Analyzer, 36 rows in BW query designer (web analyzer).
I get many rows in webi (almost like a CARTENSIAN product).
I search a round this forum but still did not see a conclusive answer to this problem.
But I see another thread that several others faced this same issue without a resolution.
My environment.
BOE XI 3.1 SP2
No fix packs
SAP IK 3.1 SP2
HPUX-IA64
Thanks in advance for any help.
Dwayne

Was this problem ever solved?
I am having a similar problem with an infoset based query.
I have created the BW infoset, and confirmed that the correct data is returned from the underlying infoproviders. A simple BW query on that infoset yields the same results.
Create the universe, and then the WEBI, and WEBI now shows hundreds of records where I expect 10. Data is being returned in WEBI that definitely shouldn't be there. It's almost like the restrictions applied in the characteristic restriction area of my BW query are being ignored, even if I include them in the WEBI query.
Cheers,
Andrew

IPhoto imports photos with wrong dates even if the dates are fine on the camera

Hi!
When I import photos with iPhoto, sometimes it imports them with wrong dates, even the dates are fine on the camera. It puts dates such as 2032. Does anyone know how can I fix that. As far as I know there is no way to change dates of the photos.
Thanks!

well that is very confusing since if the date is correct on the camera it will be correct in iPhoto
and as to
As far as I know there is no way to change dates of the photos.
Try looking through your iPhto menus - two commands - adjust time and date and batch change time and date - asjust is used to correct incorrect dates like a comera setting - Batch change for missing dates like with scans
LN

Issues with using the output redirection character with newer NXOS versions?

Has anyone seen any issues with using the output redirection character with newer NXOS versions?
Am receiving "Error 0x40870004 while copying."
Simply copying a file from bootflash to tftp is ok.
This occurs for both 3CDaemon and Tftpd32 softwares.
Have tried it on multiple switches - same issue.
Any known bugs?
thanks!
The following is an example of bad (NXOS4.1.1b) and good (SANOS3.2.1a)
MDS2# sho ver | inc system
system:    version 4.1(1b)
system image file is:    bootflash:///m9200-s2ek9-mz.4.1.1b.bin
system compile time:     10/7/2008 13:00:00 [10/11/2008 09:52:55]
MDS2# sh int br > tftp://10.73.54.194
Trying to connect to tftp server......
Connection to server Established. Copying Started.....
TFTP put operation failed:Access violation
Error 0x40870004 while copying tftp://10.73.54.194/
MDS2# copy bootflash:cpu_logfile tftp://10.73.54.194
Trying to connect to tftp server......
Connection to server Established. Copying Started.....
|
TFTP put operation was successful
MDS2#
ck-ci9216-001# sho ver | inc system
system:    version 3.2(1a)
system image file is:    bootflash:/m9200-ek9-mz.3.2.1a.bin
system compile time:     9/25/2007 18:00:00 [10/06/2007 06:46:51]
ck-ci9216-001# sh int br > tftp://10.73.54.194
Trying to connect to tftp server......
|
TFTP put operation was successful

Please check with new version of TFTPD 32 server. The error may be due to older version of TFPT server, the new version available solved this error. Files are getting uploaded with no issues.
1. Download tftpd32b.zip from:
http://tftpd32.jounin.net/tftpd32_download.html
2. Copy the tftpd32b.zip file into an empty directory and extract it.
3. Copy the file you want to transver into the directory containing tftpd32.exe.
4. Run tftpd32.exe from that directory. The "Base Directory" field should show the path to the directory containing the file you want to transfer.
At this point, the tftpserver is ready to begin serving files. As devices request files, the main tftpd32 window will log the requests.
Best Regards...

How GET Output to Excel with Oracle9i Report using OC4J

how GET Output to Excel with Oracle9i Report using OC4J.
I FINISHED THE SETPS CONCIDERING THE JSP CODE NEEDED TO GET THE EXCEL OUTPUT ON LOCAL MACHINE.
I NEED TO PUBLISH THIS REPORT THROUGH APPLICATION SERVER.
THE QUESTION IS:
1- HOW TO START AN OC4J INSTANCE FROM ORACLE 9I DS FOR THIS REPORT?
2- WHERE (PATH) TO PUBLISH THE REPORT ON THE APPLICATION SERVER?
3- WHAT IS THE DEFAULT URL TO RUN THIS REPORT AND WHERE TO PUT IT?
4- HOW TO MAKE MAPPING FOR DIRECOTRY PATH TO TRANSLATED AS URL FOR THIS REPORT?
5- IF ANY ONE CAN GIVE ME THE FULL CODE TO RUN AND CALL SIMPLE JSP REPORT TO BE VIED IN INTERNET EXPLORER.
THANK YOU

Hi,
I can't answer to all your questions, however I can tell you that:
2) The directory where to put the report file is specifiend in a file named
<serverName>.conf
in the sourceDire property
<property name="sourceDir" value="/directory/dove/mettere/i/report"/>
that you can find under ORACLE_HOME/reports/conf
3) The URL is
http://<server IAS address>:<port number>/<jsp file path>/<repName>.jsp?server=<report server name>&userid=<user>/<pwd>@<DB conn string>[&<param>=<valore>[&...]]
5) In IE you have only to set the previous URL in the address bar.
Hope this helps you
Bye
Raffy

PO created with wrong Company code

Hi Gurus,
I have Plant XXXX assigned to Company code 1111 and
Plant YYYY assigned to Company code 2222
One of the user has created PO with Plant XXXX and company code wrong as 2222.
(we have warning message setup & not error message. So, it allowed user to create PO with wrong Company code and save)
GR & IR both are already posted. I find the accounting document of these GR/IR show correct company code as XXXX-1111 (mostly would have taken correctly based on plant XXXX).
These are service POs (non stock).
Now user wants to change the company code in PO to 1111.
I checked...and system simply allow to change to company code to correct one i.e 1111. It does not give any message.
Could any one give me some additional info.. if it is right to do so? I am not too convinced at this moment.
I was suggesting user to reverse GR, IR, delete PO and create new PO. Is that right?
Thanks n advance for your input.
Best Regards,
Mohan

Dear Mohan,
U can change the company code in PO as it will not have any impact since the GR and IR is completed.
Accounts are hit based on the valution area(valuation grouping code).
Since the PO is already closed u can go ahead the change the same.
Regards,
AM Vahanan

When I connect my iPod touch it tells me that I need a new version of Apple Mobile Device Support and to uninstall iTunes and then re-install it, I've done that twice with the newest version of iTunes and it still doesn't work?

When I connect my iPod touch it tells me that I need a new version of Apple Mobile Device Support and to uninstall iTunes and then re-install it, I've done that twice with the newest version of iTunes and it still doesn't work?

Try:
Removing and reinstalling iTunes, QuickTime, and other software components for Windows Vista or Windows 7

SRM PO created with wrong company code

Hello,
The users have created several PO in SRM with wrong company code. The user was found in the wrong organization structure during the creation of shopping and approval. The PO did not get transfer to the Back because of this. Is there a way to modify the PO and change the company code.
In case we want to modify it in the tables given that BBP_PD gives you an indication of which table and entry to modify, is there a way to do this operation (like SE16N in ECC)? Have you ever done this and what risk is their in such an operation.
Thank you.

Hi,
I doubt anyone here will (or will dare) suggesting to you how to do it as it is against SAP practise totally. if the document is created wrongly, it should be deleted and approved with all the tracking and changes in place for auditing purposes.
Frankly that is what you should practise as well.. my 2cents opinion.
Regards.
YS

PO Output triggerd twice with wrong partner

Similar Messages

Maybe you are looking for