Partner profile LI and unit of measure
Hi gurus,
I am experiencing a weird situation and probably you have any clue about it.
I have configured an output to send the Purchase order information via EDI. I have used the standard function and programs to create the output. I have created the condition record for that particular vendor and output.
Then i have created the LI partner profile in we20 with the vendor number and the message types ORDERS and ORDCHG and I have also included my output with the ME10 and the ME11 in each of the messages.
When i create the PO and the output is sent I have the PO number but then i have the standard error message " Update was terminated" with the error "There is no conversion factor for material and unit of measure !" I have reviewed the PO and i have used a UoM PC that i have as an ISO code.
the point is if I use a different LI partner profile with exactly the same information then the idoc is sent without any problem. I have deleted the partner LI that I orinally created and i created it again as a copy of the one that is working but without sucess.
I have reviewed the vendor master data...but all is exactly the same.
I think or there is some config missing or that I have created the partner profile incorrectly. But it is rare that the partner profile has any link to the UoM.
Do you have any idea what it can be?
thanks so much
I understand from your mail, you have maintained the ISO equivalence to your UOM. When you change your vendor in WE20, did you change that information in MN04? This is the place where the right output type is triggered.
Other than that make sure you configured all the necessary items in WE20 -> Outbound Parameters -> process code and all otehr necessary settings.
Let me know, how it works?
Regards,
Similar Messages
-
Supplement Units of Measurement and Units of Measure
Hi All,
The company i work for, the WM system fabrics are stored in the Roll based form and in the QM module i have to create inspection lot for it. I found in the customizing "Supplement Units of Measurement and Units of Measure" which i think will help me in my process. Please explain the procedure for the "Supplement Units of Measurement and Units of Measure" in customizing.
Regards,
DTDhttp://help.sap.com/erp2005_ehp_04/helpdata/EN/c6/f83bb94afa11d182b90000e829fbfe/frameset.htm
-
Oracle and EPSG and Units Of Measure tabel.
I believe there is a wrong value in the Oracle 11g Enterprise database on Windows 64 bit.
We installed this a couple of months ago and found out that the Units Of Measure table is different from a Oracle 10g.
Here is what I think is wrong.
Oracle 10g Express Edition
9101 radian Radian angle 9101 1 1 ISO 1000:1992 EPSG FALSE
9102 degree Decimal Degree angle 9101 3.14159265358979 180 EPSG FALSE
9103 arc-minute angle 9101 3.14159265358979 10800 EPSG FALSE
9104 arc-second angle 9101 3.14159265358979 648000 EPSG FALSE
9105 grad angle 9101 3.14159265358979 200 EPSG FALSE
9106 gon angle 9101 3.14159265358979 200 EPSG FALSE
9107 degree minute second angle 9102 EPSG EPSG FALSE
9108 degree minute second hemisphere angle 9102 EPSG EPSG FALSE
9109 microradian angle 9101 1 1000000 ISO 1000. EPSG FALSE
9110 sexagesimal DMS angle 9102 EPSG EPSG FALSE Oracle 11g Enterprise
9101 radian Radian angle 9101 1 1 ISO 1000:1992 EPSG FALSE
9102 degree Decimal Degree angle 9101 3,14159265358979 180 EPSG FALSE
9103 arc-minute angle 9101 3,14159265358979 10800 EPSG FALSE
9104 arc-second angle 9101 3,14159265358979 648000 EPSG FALSE
9105 grad angle 9101 3,14159265358979 200 EPSG FALSE
9106 gon angle 9101 3,14159265358979 200 EPSG FALSE
9107 degree minute second angle 9101 EPSG EPSG FALSE
9108 degree minute second hemisphere angle 9101 EPSG EPSG FALSE
9109 microradian angle 9101 1 1000000 ISO 1000. EPSG FALSE
9110 sexagesimal DMS angle 9101 EPSG EPSG FALSE It is all about the conversion from 9110 to 9101.
11g tells me do nothing.
While 10g tells me to go via 9102, which in the end does pi/180.0.
I've checked EPSG v6.17 (Access database) which is similar as 10g.
Is it a know bug in Oracle 11g (why change it in the first place? it was correct).I filed this as a bug (9534127), and it's fixed.
The following is the workaround (as mentioned in the bug description):
begin
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
uom_id = 9107; -- degree minute second, based on 9102
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
uom_id = 9108; -- degree minute second hemisphere, based on 9102
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
uom_id = 9110; -- sexagesimal DMS, based on 9102
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
uom_id = 9111; -- sexagesimal DM, based on 9102
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
uom_id = 9203; -- coefficient, based on 9201
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
uom_id = 9115; -- degree minute, based on 9102
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
uom_id = 9116; -- degree hemisphere, based on 9102
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
uom_id = 9117; -- hemisphere degree, based on 9102
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
uom_id = 9118; -- degree minute hemisphere, based on 9102
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
uom_id = 9119; -- hemisphere degree minute, based on 9102
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
uom_id = 9120; -- hemisphere degree minute second, based on 9102
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
uom_id = 9121; -- sexagesimal DMS.s, based on 9102
end;
begin
update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
= 180, target_uom_id = 9101 where uom_id = 9107; -- degree minute second,
based on 9102
update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
= 180, target_uom_id = 9101 where uom_id = 9108; -- degree minute second
hemisphere, based on 9102
update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
= 180, target_uom_id = 9101 where uom_id = 9110; -- sexagesimal DMS, based on
9102
update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
= 180, target_uom_id = 9101 where uom_id = 9111; -- sexagesimal DM, based on
9102
update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
= 180, target_uom_id = 9101 where uom_id = 9115; -- degree minute, based on
9102
update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
= 180, target_uom_id = 9101 where uom_id = 9116; -- degree hemisphere, based
on 9102
update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
= 180, target_uom_id = 9101 where uom_id = 9117; -- hemisphere degree, based
on 9102
update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
= 180, target_uom_id = 9101 where uom_id = 9118; -- degree minute hemisphere,
based on 9102
update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
= 180, target_uom_id = 9101 where uom_id = 9119; -- hemisphere degree minute,
based on 9102
update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
= 180, target_uom_id = 9101 where uom_id = 9120; -- hemisphere degree minute
second, based on 9102
update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
= 180, target_uom_id = 9101 where uom_id = 9121; -- sexagesimal DMS.s, based
on 9102
end;
begin
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1,
target_uom_id = 9001 where uom_id = 10031; -- Meter, based on 10032
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1,
target_uom_id = 9001 where uom_id = 10032; -- Meter, based on 10032
update mdsys.sdo_units_of_measure set factor_b = 1000, factor_c = 1,
target_uom_id = 9001 where uom_id = 10033; -- Kilometer, based on 10032
update mdsys.sdo_units_of_measure set factor_b = 1000, factor_c = 1,
target_uom_id = 9001 where uom_id = 10034; -- Kilometer, based on 10032
update mdsys.sdo_units_of_measure set factor_b = .01, factor_c = 1,
target_uom_id = 9001 where uom_id = 10035; -- Centimeter, based on 10032
update mdsys.sdo_units_of_measure set factor_b = .01, factor_c = 1,
target_uom_id = 9001 where uom_id = 10036; -- Centimeter, based on 10032
update mdsys.sdo_units_of_measure set factor_b = .001, factor_c = 1,
target_uom_id = 9001 where uom_id = 10037; -- Millimeter, based on 10032
update mdsys.sdo_units_of_measure set factor_b = .001, factor_c = 1,
target_uom_id = 9001 where uom_id = 10038; -- Millimeter, based on 10032
update mdsys.sdo_units_of_measure set factor_b = 1609.344, factor_c = 1,
target_uom_id = 9001 where uom_id = 10039; -- Mile, based on 10032
update mdsys.sdo_units_of_measure set factor_b = 1852, factor_c = 1,
target_uom_id = 9001 where uom_id = 10040; -- Nautical Mile, based on 10032
update mdsys.sdo_units_of_measure set factor_b = .3048006096012, factor_c =
1, target_uom_id = 9001 where uom_id = 10041; -- U.S. Foot, based on 10032
update mdsys.sdo_units_of_measure set factor_b = .3048, factor_c = 1,
target_uom_id = 9001 where uom_id = 10042; -- Foot (International), based on
10032
update mdsys.sdo_units_of_measure set factor_b = .0254, factor_c = 1,
target_uom_id = 9001 where uom_id = 10043; -- Inch, based on 10032
update mdsys.sdo_units_of_measure set factor_b = .9144, factor_c = 1,
target_uom_id = 9001 where uom_id = 10044; -- Yard, based on 10032
update mdsys.sdo_units_of_measure set factor_b = 20.1168, factor_c = 1,
target_uom_id = 9001 where uom_id = 10045; -- Chain, based on 10032
update mdsys.sdo_units_of_measure set factor_b = 5.0292, factor_c = 1,
target_uom_id = 9001 where uom_id = 10046; -- Rod, based on 10032
update mdsys.sdo_units_of_measure set factor_b =
.20116619497596571965479068149417, factor_c = 1, target_uom_id = 9001 where
uom_id = 10047; -- Link, based on 10032
update mdsys.sdo_units_of_measure set factor_b =
.30481225298450596901193802387605, factor_c = 1, target_uom_id = 9001 where
uom_id = 10048; -- Modified American Foot, based on 10032
update mdsys.sdo_units_of_measure set factor_b =
.30479726511509957523453133559723, factor_c = 1, target_uom_id = 9001 where
uom_id = 10049; -- Clarke's Foot, based on 10032
update mdsys.sdo_units_of_measure set factor_b =
.30479951799004225054718498468167, factor_c = 1, target_uom_id = 9001 where
uom_id = 10050; -- Indian Foot, based on 10032
update mdsys.sdo_units_of_measure set factor_b =
.20116782494375873394114972441151, factor_c = 1, target_uom_id = 9001 where
uom_id = 10051; -- Link (Benoit), based on 10032
update mdsys.sdo_units_of_measure set factor_b =
.20116765121552632252046201402296, factor_c = 1, target_uom_id = 9001 where
uom_id = 10052; -- Link (Sears), based on 10032
update mdsys.sdo_units_of_measure set factor_b =
20.116782494375873394114972441151, factor_c = 1, target_uom_id = 9001 where
uom_id = 10053; -- Chain (Benoit), based on 10032
update mdsys.sdo_units_of_measure set factor_b =
20.116765121552632252046201402296, factor_c = 1, target_uom_id = 9001 where
uom_id = 10054; -- Chain (Sears), based on 10032
update mdsys.sdo_units_of_measure set factor_b =
.914398553970126751641554954045, factor_c = 1, target_uom_id = 9001 where
uom_id = 10055; -- Yard (Indian), based on 10032
update mdsys.sdo_units_of_measure set factor_b =
.91439841461602873872937279101345, factor_c = 1, target_uom_id = 9001 where
uom_id = 10056; -- Yard (Sears), based on 10032
update mdsys.sdo_units_of_measure set factor_b = 1.8288, factor_c = 1,
target_uom_id = 9001 where uom_id = 10057; -- Fathom, based on 10032
end;
begin
update mdsys.sdo_units_of_measure set factor_b =
.017453292519943295769236907684886, factor_c = 1, target_uom_id = 9101 where
uom_id = 10001; -- Decimal Degree, based on 10002
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1,
target_uom_id = 9101 where uom_id = 10002; -- Radian, based on 10002
update mdsys.sdo_units_of_measure set factor_b =
.0000048481368110953599358991410235795, factor_c = 1, target_uom_id = 9101
where uom_id = 10003; -- Decimal Second, based on 10002
update mdsys.sdo_units_of_measure set factor_b =
.00029088820866572159615394846141477, factor_c = 1, target_uom_id = 9101
where uom_id = 10004; -- Decimal Minute, based on 10002
update mdsys.sdo_units_of_measure set factor_b =
.015707963267948966192313216916398, factor_c = 1, target_uom_id = 9101 where
uom_id = 10005; -- Gon, based on 10002
update mdsys.sdo_units_of_measure set factor_b =
.015707963267948966192313216916398, factor_c = 1, target_uom_id = 9101 where
uom_id = 10006; -- Grad, based on 10002
end;
/ -
Change Material Number and unit of measure
Can we change material code and / or its Unit of measure . Please help
http://sap-img.com/materials/change-base-unit-of-measure.htm
Re: change material code
Change of unit of measure -
Material Master IDOC MATMAS05 and unit of measure
Hi
We are using SAP standard material master IDOC type MATMAS05 to trigger IDOC. Our material master is having base unit of measure as "G". We are not using ISO unit of measurement. But Material master IDOC, segment E1MARM is populating base unit of meaurement (MEINS) as "GRM".
Any idea why IDOC is picking ISO unit of measurement instead of material master base unit of measurement.
Any idea how to send base unit of measurememt as "G" instead of "GRM" in DOC segment.
Thanks
NileshThats the way it works. In any interfacie to or from external sys. , it uses the ISO code from CUNI instead of the UOM .
-
What is PDC in partner profile? and PDC time req. ID card
Hi all,
These are actually tabs when you click F4 on agent in WE20 (partner profile). What is PDC? Please point me to related files or threads.
Thanks,
Charles.Hi,
Please check this online document.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ed60b490-0201-0010-dc82-8bea16db1dfd
Regards,
Ferry Lianto -
Regarding partner profiles LI and KU
Hi,
I need to send a PO created in one SAP system to a vendor system where it needs to create SO automatically.In this senario which partner type i need to use for outbound and which partner type i need to use for inbound ....(i.e in LI and KU which is used for outbound and which is used for inbound)
Thanks&Regards
Giridhar KarnamHello Giridhar,
In Outbound settings we need to select partner type as LI and Inbound settings we need to select partner type as KU in this Scenario.
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b809b43d711d1893e0000e8323c4f/frameset.htm
Above scenario is beautifully explained in the following blog. Refer this
/people/srinivas.vanamala2/blog/2006/12/11/edi-basics
Regards
Srikanth
<i>Reward me if helpful</i><u></u> -
Invalid vales of characteristic and units of measure
Hello,
During the data load the system generated the following messages :
1. No SID found for value 'CBM' of characteristic 0VOLUMEUNIT
2. Value "X%X'''" (like that) of characteristic contents invalid letters
What do you reccomend to do?hi,
check table t006a if CBM is there.
if you load from r/3, you may need to transfer from r/3, by rsa1 > source system > right click 'transfer global setting'.
you can maintain the unit use transaction CUNI. -
IDocs, INVOIC partner profile configuration
Hi,
I need to receive the INVOIC IDocs from sender system.
Sender(S) system is new system
receiver(R) system is already exisitng system.
I tried to configure the inbound settings in receiver syste. But message type INVOIC, process code INVL, FM all are already available and configured for some ohter systems.
Now if i configure only partner profiles and distribution model, then is it work.
Thanks
KiranKiran,
INOVOIC, INVL, Process codes etc come with the standard system. They can be configured for any partner profile and any sender system.
First, you need to determine the inbound connection. Will the new sender system (S) going to follow the same RFC connection already setup for other sender systems? E.g. Are all the inbound IDOC's flowing through PI or a single EAI system?
If yes, then you just need to setup a new partner profile and use the same port already setup for your existing connections.
If no, then you have to determine how the sender system will connect with SAP. Will they drop files in the SAP's application server? After dropping can they execute the startrfc.exe with required parameters. If they can then you can just proceed with creation of a port to listen that folder (assuming the RFC connection is already setup for that connection) and move ahead with partner profile creation and other mandatory setups. If they cannot trigger the startrfc.exe, then you have to define a new RFC destination (SM59) and a new port (WE21) to read data for this RFC destination. You have to determine when to read the data (e.g. explicit host type etc). -
File to IDOC - issue with partner profile
I have done File to IDOC scenario and tested it end to end successfully. For same have done all require configuration setting in R/3 like defining logical System and partner profile. And it sends new IDOC successfully in R/3 with status code 50 (IDoc added).
But when I create new logical system and partner profile in R/3 and when I use same logical system in my above mention scenario then my new generate IDOC in R/3 return status code 56 (EDI: Partner profile inbound not available). But same scenario work fine with my earlier partner profile. Here I have done all require changes at adapter level like adapter specific identification and same new logical system I have update in SLD with my business system Logical System Name.Hi Bhavesh,
Thanks for your reply.
In control record, I checked with sender and receiver partner. In this sender partner is new partner profile which I have created with port details. Receiver partner has logical system name which I have mentioned in my SLD for my receiver business system. But in receiver partner dont have any port details.
But still it has same problem.
-Sunil -
Partner Profile settings for IDOCs
Hi,
when i posted the IDOC, it left the status 51.
i think which means "Application not posted".
do i need to change the partner profile!
if yes please let me know how to change that.
its very urgent please.
thanks in advance.
Regards,
ravi.As mentioned in the earlier reply you need to check idoc listing WE02.
You may also want to look into the partner profile- WE20 and see if what you are trying to pass thru has been set up correctly. Make sure the correct port is defined along with the partner details.
If you need to edit the IDoc , you can do it from WE02 by clicking on the segment and then going into the Change mode. The other option of re- processing Idocs is using the testing tool- WE19 or the re-process Idocs BD87 transactions. -
BDLS: Partner profiles not change - System Landscape Copy (SRM+HCM+ERP)
Hello,
Can anybody help me for system copy i.e. production to quality.
System Landscape:
- 1 central HCM System
- 1 central SRM System
- 6 Backend Systems (ERP)
Problem: Change Log. Systemnames (SALE) and Partner Profiles (WE20) and ALE-Distribution Model (BD64).
We run BDLS (change RFC/log.Systemnames/ change BD64), but we have problems with Partner Profiles (WE20). Which do not change !
Anybody knows this problem?
What can I do?
Thanks, SilkeRunning BDLS would not normally revert the setting for the partner profiles. You could either load it again via backup transport or make new entries accordingly to the specific settings prior to the system copy.
-
Hi,
Please can any one send me details about partner profiles usage and the tcode where exactly we have to maintain this.
If anyone have documentation on AlE is added advantage for me.
Regards,
KotiHi,
Logical System name is used to indicate the application system to which you are sending the data. Partner profiles use the above Logical System name to determine the system to which the data is to be sent ie you have to tell wether inbound or outbound.
Below are the links for ALE IDOC related materials.
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
/people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)
Reward points if useful.
Regards,
Soumya. -
Error creating partner profiles using we20
hi friends,
I am trying to create a new partner profile from an existing one..but it giving me an error <b>"Please enter a permitted partner number"...</b> but when i give another number its accepting....
can someone help me understand what am i missing?
cheers
charlieHi
assign the partner profile number in fi12 and save then click on the partner profile button and copy the partner profile u want and create a new one and save.
Regards
genie -
Partner Profiles overwritten by TDMS-Copy
Hello,
our TDMS-Copy succeeded by overwriting an old client, but copied Partner Profiles (WE20) and Ports (WE21) too, which we didnu2019t want to be changed. Is there a way to save this data?
Regards
p121848Hi,
The table names are
TBD00 EDIMSG
EDP21
EDP13
EDP12
EDIDD
EDIPHONE
EDP13
EDP21
EDPP1
EDMAT
EDMA
EDADM
EDAYTYPBLOCK
EDAYTYPBLOCKDEF
EDAYTYPBLOCKT
EDAYTYPE
EDAYTYPET
EDBDMSKY
EDCPIC
EDE1T
EDE2T
EDE5T
EDE6T
EDEREGPARCONF
EDEREGPARCONFT
EDEREGPARVAL
EDEREGPODGROUP
EDEREGPODGROUPT
EDEREGPROCPARDIS
EDEREGSCENAGREE
EDEREGSCENARIO
EDEREGSCENARIOT
EDEREGSCENCONTR
EDEREGSCENCONTRT
EDEREGSCENDATEX
EDEREGSCENSERV
EDEREGSCENSERVT
EDEREGSPAGREE
EDEREGSWITCHDIAL
EDEREGSWITCHPROC
EDEREGSWITCHSYST
EDEREG_SERIDENT
EDEREG_SERIDENTT
TBD001
TBD002
TBD00T
TBD03
TBD05
TBD06
TBD20
TBD30
TBD40
TBD41
TBD52
TBD55
TBD56
TBD61
TBD611
TBD61B
TBD62
TBD71
TBD71T
TBD72
TBD73
TBD74
TBDA1
TBDA2
TBDBANKC
TBDBR
TBDBRF
TBDC001
TBDC002
TBDIBAN
TBDLI
TBDLT
TBDMO
TBDMO_DET
TBDRCSTATE
TBDSE
TBDSET
EDEREG_SIDPRO
EDEREG_SIDPROINT
EDEREG_SIDPROT
EDEVCHECK_BACKUP
EDEVGR
EDEXCOMMFORMALE
EDEXCOMMFORMAT
EDEXCOMMFORMATT
EDEXCOMMFORMFTP
EDEXCOMMFORMINTR
EDEXCOMMFORMMAIL
EDEXCOMMFORMPART
EDEXCOMMFORMVERS
EDEXCOMMFORMXML
EDEXCOMMMAILADDR
EDEXDEFSERVPROV
EDEXDEFUI
EDEXDUECONTR
EDEXDUECONTRT
EDEXIDOCSEND
EDEXIDOCSENDT
EDEXPROC
EDEXPROCPAR
EDEXPROCPODGEN
EDEXPROCSPGEN
EDEXPROCT
EDEXPROCUI
EDEXTASK
EDEXTASKASS
EDEXTASKERROR
EDEXTASKIDOC
EDEXTASKREF
EDEXTASKWKFLOW
EDGE
EDICONFIG
EDID3
EDIDD_OLD
EDIDOCINDX
EDILOGADR
EDIPHONE
EDIPO2
EDIPOA
EDIPOACODPAG
EDIPOD
EDIPOF
EDIPOI
EDIPORT
EDIPOX
EDIPOXH
EDIPOXU
EDIQI
EDIQO
EDISCACT
EDISCDOC
EDISCOBJ
EDISCOBJH
EDISCORDSTATE
EDISCORDSTATET
EDISCPOS
EDISCREMOV
EDISCTYPE
EDISCTYPET
EDISCVAR
EDISCVART
EDIVDIM
EDI_MONIT
EDLTYP
EDMMS
EDMS_AT01
EDMS_CONDITION
EDMS_CT01
EDMS_CT01T
EDMS_FILTER
EDMS_LAYOUT
EDMS_LAY_DETAIL
EDMS_PREFS
EDP12
EDP13
EDP21
EDPAR
EDPI1
EDPO1
EDPO3
EDPP1
EDPPV
EDPST
EDPVW
EDRGPODGRASSIG
EDRGSPAGRTYPE
EDRGSPAGRTYPET
EDSC
EDSCH
EDSCHINDEXA
EDSCT
EDSDC
These tables are involved in transaction We20 and Bd64
Maybe you are looking for
-
I somehow changed the pointer / cursor in bridge from an arrow to a small magnifying glass... when i position the cursor / pointer on a picture in the PREVIEW panel in bridge and press on the left mouse key, the cursor is a small magnifying glass tha
-
Hi , In a dashboard i have created a prompt ,i.e MOnth. If i select month from drop down list we will get only one month data right, but my requirement is if i select one month in prompt i need to display six monthdata. How is it possible? Waiting fo
-
Hi, I have report Quantity all material, the etXX is included in the range NXX and AXX is not assigned. We would like to create a new product group u201CNEWGR1lu201D and include etXX and AXX . please give instrauction whay should I check first, then
-
Photoshop CS6 Crashing and acting erratically while working with 3D
So,.. CS6 keeps crashing and doing crazy things on me while working on my 2D/3D composite digital room setting. It seems to me like what's causing most of the crashing is the materials. Here's the problems: - Crashes constantly while simply trying to
-
Inventory to determine size of a folder on workstation
I am trying to see if I can determine the size of a folder on an inventoried workstation. I am trying to find a way to determine the size of the GW archive folder (always named of???arc). Is this possible? thanks