Document No of 103 &105 Mtype to be Same
Dear Friends,
I am mapping the Gate Entry scenario by splitting the receipt with movement types 103 and 105. But my concern is, I will be getting two different document numbers for each transaction,i.e One each for 103 movement type and 105 movement type.
Pls suggest me if there is any way where in I release the GR Block stock ( MType 105) in same document number. Urgent reply will be rewarded accordingly. Thanks.. Shash
hi
Not at all Possible...
Regards
S.Baskaran
Similar Messages
-
Reference document number of 103 movement not seen in 105 movement documnt
Dear all,
I have made a material document with movement type 105 with reference to 103 document.
After creation, the field LFBNR in the 105 document is not updated with the 103 document number.
In all other cases the document number of 103 movements are updated in the the field of 105 document.
Can anybody can share me if you have any information about this scenario and what would be the solution.
Thanks....
Hari.Hi Murugan,
I am giving you more clarification.
I have created a Good Receipt through MIGO using 103 movement. Later I have created 105 movement with respect to 103 movement reference through release blocked stock.
After creation of documents, when checked the document created through 105 movement there is no reference number of 103 document number found in the document number of 105 movement.
In the table MSEG field LFBNR is supposed to get updated with the reference number of the document created through 103 movement.
In this case, this reference number is not updated in the table MSEG-LFBNR.
My question is that how the document with 105 movement get posted without the reference of document of 103 movement and what would be the reason.
Hope the question is clear.
Awaiting for your replies.
Thanksss....Hari.
Edited by: Harikrishnan_sap on Nov 13, 2009 2:02 AM -
Dear All
We are Following 103 & 105 process for goods receipts , But we are facing some Problems in stadard process as follows
1. while Posting MIRO for PO having Both 103 & 105 movement it is showing 103 Document as referance document in MIRO .But Our requirement is to show 105 document as accouting entries are happing only at the time of 105
How can I Update 105 document Number In this Field
2. I want Pending Invoices Report ( MIGO done But MIRO not done ) MR11 is giving ressult as per requirement , Here Aslo I am
Getting referance Document as 103 number which is not Useful for user , Here also i want 105 document Number Or accounting Document Number of 105 as referance document
How can i get this
these Issue are very cretical for Business ,
Please Provoide Suggetion
Thanks & regards
AdvaitHi,
Movement 103 and 105 are used in case of Gr blocked stock. Movemnet type 103 is used when there is conditional acceptance for the material. For example material ordered from vendor , for which quality certficate is not recieved. So goods are taken i conditional accepatnce with movement type 103 , For Gr blocked stock , goods remains non valauted and also quantity still remains open ordered quantity. After recieveing the certicate for gr blocked stock the material is accepted with movement type 105.
So there is no question of generating a accounting document with movement type 103. To get the desired results I suggest you to make the goods acceptable with movement ype 105 by keeping material document as reference which is generated during 103 in MIGO.
Regards,
Tushar Patankar -
Dear Gurus,
Is there any report which will show the status of 103 mvt type.How to check whether 105 is done or not. There are alot of documents.
Regards,
KumarIn ME2M enter selection Parameter as "WE104" , then system will display only those documents in which 103 qty > 105 qty , i.e. 105 is pending to be done.
-
I have created a PO with text.I have doen 103.When i try to key in the PO number & do 105,the system says document does not contain selectable items.
Does 103 & 105 option will not work with item text?Hi,
In MIGO choose---- release GR blocked stock----material doc & then choose 105 material movement type. It will work. Choose correct material doc number.
Regards,
Alok Tiwari -
RG23A PARTI & PARTII register & tab is not updating in MIGO by 103 105 mvt
Hi Experts,
I am doing MIGO by 103 & 105 movements. My problem is RG23A PARTI & PARTII register is not updating & also in Detail DATA (below the header details tab) Excise ITEM tab is also not coming.
I have done the configuration like LOG GEN->Tax on Goods Movements ->under business transcations->Incoming excise details->specify movement types involve in excise invoices.
Actually, after doing MIGO PARTI is updated in table J_1IPART1 but no values updated for J_1IPART2.
Can anybody help me?
Thanks
TruptiHello
as per you part1 values updationg while doing the time of migo and part2 values not updating while doing the j1iex post .
your not getting the excise tab on details so check the tax code mentioned in po assigned the co code or not ?
if your using the TAXINN procedure check the condition records in fv12.
check the j1id settings for material and vendor.
Regards
Laxman -
Hi Experts,
We are having multuple units for receiving material and centra stores for processing GRVs.
We want to use 103 & 105 movement type instead 101. Facing following problems
1. Many times Excise Invoice is not received alongwith material and hence not able to enter excise amount immediately.
2. Excise amount once entered can't be changed later on.
3. Physical received quantity may change, which need to be recorded in GRV.
4. Actual details change many times, which need to be recorded in GRV. Can anybody please provide solution,especialy for
point 1&2 asap ?
Thnx n rgds,
Sanjay MungeeDo not book the Excise at the time of MIGO, at the time MIGO just enter Part 1 if needed actual value(Part 2) you can post by J1IEX, when you get the proper excise Invoice then book it with J1IEX refering your MIGO details.
-
Hi Experts,
Can you please tell me how these two mvt type 103 & 105 works.Please tell me some scenerio
ARHi Rana,
1) Movement Type - 103 Goods receipt for purchase order into GR blocked stock means not approved by Quality dept.for ready
to use.
(Ex. PO Qty - 10 Nos. ordered, 7 Nos. accepted by quality dept. & stock accounted with 101 Mvtype and 3 Nos. are not
accepted by Quality dept. & stock accounted with 103 Mvtype in GR blocked stock)
2) Movement Type - 105 Release from GR blocked stock for purchase order means approved by Quality dept. from GR blocked
stock. (From the above example 3 Nos. GR blcoked stock, after 100% quality inspection 2 Nos. released from GR blocked
& stock account 101 Mvtype for ready to use. 1 No. rejected & return to vendor with 122 Mvtype).
Hope, it is clear for you.
Thanks and Regards,
K.Rajendran. -
XML document structures must start and end within the same entity
Hi there,
I'm working with a client/server application and using SaxParser for reading in xml. I get the SaxParserException: XML document structures must start and end within the same entity. I understand what that means, but it isn't applicable! The xml data being used is well-formed. I checked the well-formedness with Stylus Studio to make sure. Here's the data:
<?xml version='1.0' encoding='UTF-8'?>
<vcmessage>
<vcsource>3</vcsource>
<processevent>16</processevent>
<shape>
<llindex>0</llindex>
<shapetype>9</shapetype>
<shapeproperties>
<shapelocation>
<xcoord>54</xcoord>
<ycoord>184</ycoord>
</shapelocation>
<bounds>
<width>24</width>
<height>24</height>
</bounds>
<fgcolor>
<fgred>0</fgred>
<fggreen>0</fggreen>
<fgblue>0</fgblue>
</fgcolor>
<bgcolor>
<bgred>255</bgred>
<bggreen>255</bggreen>
<bgblue>255</bgblue>
</bgcolor>
<thickness>1</thickness>
<isfilled>false</isfilled>
</shapeproperties>
</shape>
</vcmessage>The parser generally stops around the </bgcolor> tag.
I'm using Eclypse as my IDE. I'm wondering if there's something wrong with it? Or maybe there's something wrong with the class I'm using for reading in the XML? Followng is the class.
Please advise,
Alan
package vcclient;
import java.io.*;
import org.xml.sax.*;
import org.xml.sax.helpers.*;
import javax.xml.parsers.*;
public class XMLDocumentReader extends DefaultHandler
private VCClient client = null;
private Writer out;
private String lineEnd = System.getProperty("line.separator");
private boolean haveSourceType = false;
private boolean haveUserName = false;
private boolean haveMessage = false;
private boolean haveProcessEvent = false;
private boolean haveLinkedListIndex = false;
private boolean haveOpeningShapePropertiesTag = false;
private boolean haveShapeType = false;
private boolean haveOpeningShapeLocationTag = false;
private boolean haveShapeLocation = false;
private boolean haveOpeningXCoordTag = false;
private boolean haveOpeningYCoordTag = false;
private boolean haveOpeningBoundsTag = false;
private boolean haveBoundsWidth = false;
private boolean haveBoundsHeight = false;
private boolean haveOpeningFGColorTag = false;
private boolean haveOpeningBGColorTag = false;
private boolean haveOpeningThicknessTag = false;
private boolean haveOpeningIsFilledTag = false;
private boolean haveOpeningImageDataTag = false;
private boolean haveOpeningTextDataTag = false;
private boolean haveFGRed = false;
private boolean haveFGGreen = false;
private boolean haveFGBlue = false;
private boolean haveBGRed = false;
private boolean haveBGGreen = false;
private boolean haveBGBlue = false;
private boolean haveThickness = false;
private boolean haveIsFilled = false;
private boolean haveImageData = false;
private boolean haveTextData = false;
private VCMessage vcmessage = null;
public XMLDocumentReader(VCClient value)
client = value;
vcmessage = new VCMessage();
public VCMessage getVCMessage()
return vcmessage;
public boolean haveSourceType()
return haveSourceType;
public boolean ParseXML(InputStream stream)
boolean success = false;
// Use the default (non-validating) parser
SAXParserFactory factory = SAXParserFactory.newInstance();
try
// Set up output stream
out = new OutputStreamWriter(System.out, "UTF-8");
// Parse the input
SAXParser saxParser = factory.newSAXParser();
saxParser.parse( stream, this );
success = true;
catch (SAXParseException spe)
// Error generated by the parser
System.out.println("\n** Parsing error"
+ ", line " + spe.getLineNumber()
+ ", uri " + spe.getSystemId());
System.out.println(" " + spe.getMessage() );
// Unpack the delivered exception to get the exception it contains
Exception x = spe;
if (spe.getException() != null)
x = spe.getException();
x.printStackTrace();
return success;
catch (SAXException sxe)
// Error generated by this application
// (or a parser-initialization error)
Exception x = sxe;
if (sxe.getException() != null)
x = sxe.getException();
x.printStackTrace();
return success;
catch (ParserConfigurationException pce)
// Parser with specified options can't be built
pce.printStackTrace();
return success;
catch (Throwable t)
t.printStackTrace();
return success;
return success;
public void startDocument()throws SAXException
emit("<?xml version='1.0' encoding='UTF-8'?>");
nl();
public void endDocument()throws SAXException
try {
nl();
out.flush();
} catch (IOException e) {
throw new SAXException("I/O error", e);
public void startElement(String namespaceURI,
String lName, // local name
String qName, // qualified name
Attributes attrs)throws SAXException
String eName = lName; // element name
if (eName.equals(""))
eName = qName; // namespaceAware = false
emit("<"+eName);
if (attrs != null) {
for (int i = 0; i < attrs.getLength(); i++) {
String aName = attrs.getLocalName(i); // Attr name
if (aName.equals("")) aName = attrs.getQName(i);
emit(" ");
emit(aName + "=\"" + attrs.getValue(i) + "\"");
emit(">");
if(makeStartTag(eName).equals(Constants.OPENING_SHAPEPROPERTIES))
haveOpeningShapePropertiesTag = true;
else if(makeStartTag(eName).equals(Constants.OPENING_SHAPELOCATION))
haveOpeningShapeLocationTag = true;
else if(makeStartTag(eName).equals(Constants.OPENING_BOUNDS))
haveOpeningBoundsTag = true;
else if(makeStartTag(eName).equals(Constants.OPENING_FGCOLOR))
haveOpeningFGColorTag = true;
else if(makeStartTag(eName).equals(Constants.OPENING_BGCOLOR))
haveOpeningBGColorTag = true;
else if(makeStartTag(eName).equals(Constants.OPENING_BGGREEN))
System.out.println("See BGGreen");
else if(makeStartTag(eName).equals(Constants.OPENING_BGBLUE))
System.out.println("See BGBlue");
else if(makeStartTag(eName).equals(Constants.OPENING_THICKNESS))
haveOpeningThicknessTag = true;
else if(makeStartTag(eName).equals(Constants.OPENING_ISFILLED))
haveOpeningIsFilledTag = true;
else if(makeStartTag(eName).equals(Constants.OPENING_IMAGEDATA))
haveOpeningImageDataTag = true;
else if(makeStartTag(eName).equals(Constants.OPENING_TEXTDATA))
haveOpeningTextDataTag = true;
public void endElement(String namespaceURI,
String sName, // simple name
String qName // qualified name
)throws SAXException
if(sName.equals("") && !qName.equals(""))
sName = qName;
emit("</"+sName+">");
else
emit("</"+sName+">");
if(makeEndTag(sName).equals(Constants.CLOSING_SOURCE_TYPE))
haveSourceType = true;
else if(makeEndTag(sName).equals(Constants.CLOSING_USER))
haveUserName = true;
else if(makeEndTag(sName).equals(Constants.CLOSING_MESSAGE))
haveMessage = true;
else if(makeEndTag(sName).equals(Constants.CLOSING_PROCESSEVENT))
haveProcessEvent = true;
else if(makeEndTag(sName).equals(Constants.CLOSING_LINKEDLISTINDEX))
haveLinkedListIndex = true;
else if(makeEndTag(sName).equals(Constants.CLOSING_SHAPETYPE))
haveShapeType = true;
else if(makeEndTag(sName).equals(Constants.CLOSING_SHAPELOCATION))
haveOpeningShapeLocationTag = false;
else if(makeEndTag(sName).equals(Constants.CLOSING_WIDTH))
haveBoundsWidth = true;
else if(makeEndTag(sName).equals(Constants.CLOSING_HEIGHT))
haveBoundsHeight = true;
else if(makeEndTag(sName).equals(Constants.CLOSING_BOUNDS))
haveOpeningBoundsTag = false;
else if(makeEndTag(sName).equals(Constants.CLOSING_FGRED))
haveFGRed = true;
else if(makeEndTag(sName).equals(Constants.CLOSING_FGGREEN))
haveFGGreen = true;
else if(makeEndTag(sName).equals(Constants.CLOSING_FGBLUE))
haveFGBlue = true;
else if(makeEndTag(sName).equals(Constants.CLOSING_FGCOLOR))
haveOpeningFGColorTag = false;
else if(makeEndTag(sName).equals(Constants.CLOSING_BGRED))
haveBGRed = true;
else if(makeEndTag(sName).equals(Constants.CLOSING_BGGREEN))
haveBGGreen = true;
else if(makeEndTag(sName).equals(Constants.CLOSING_BGBLUE))
System.out.println("See closing BGBlue");
haveBGBlue = true;
else if(makeEndTag(sName).equals(Constants.CLOSING_BGCOLOR))
haveOpeningBGColorTag = false;
else if(makeEndTag(sName).equals(Constants.CLOSING_THICKNESS))
System.out.println("XMLDocumentReader: Step2");
haveOpeningThicknessTag = false;
else if(makeEndTag(sName).equals(Constants.CLOSING_ISFILLED))
haveOpeningIsFilledTag = false;
else if(makeEndTag(sName).equals(Constants.CLOSING_IMAGEDATA))
haveOpeningImageDataTag = false;
else if(makeEndTag(sName).equals(Constants.CLOSING_TEXTDATA))
haveOpeningTextDataTag = false;
private String makeStartTag(String tag_name)
String start = "<";
String end = ">";
return start.concat(tag_name).concat(end);
private String makeEndTag(String tag_name)
String start = "</";
String end = ">";
return start.concat(tag_name).concat(end);
public void characters(char buf[], int offset, int len)throws SAXException
String s = new String(buf, offset, len);
if(haveSourceType == false)
if(vcmessage.getSourceType() == null)
try
if(s.equals(""))return;
int sourcetype = Integer.parseInt(s);
vcmessage.setSourceType(sourcetype);
catch(NumberFormatException nfe){}
else if(vcmessage.getSourceType() == SourceType.CHAT_SOURCE)
if(vcmessage.getSourceType() == SourceType.CHAT_SOURCE && haveUserName == false)
vcmessage.setUserName(s);
else if(vcmessage.getSourceType() == SourceType.CHAT_SOURCE && haveMessage == false)
//When the parser encounters interpreted characters like: & or <,
//then this method gets invoked more than once for the whole message.
//Therefore, we need to concatonate each portion of the message. The
//following method call automatically concatonates.
vcmessage.concatMessage(s);
else if(vcmessage.getSourceType() == SourceType.WHITEBOARD_SOURCE)
if(haveProcessEvent == false)
try
vcmessage.setProcessEvent(Integer.parseInt(s));
catch(NumberFormatException nfe){}
else if(haveLinkedListIndex == false)
try
vcmessage.setLinkedListIndex(Integer.parseInt(s));
catch(NumberFormatException nfe){}
else if(haveShapeType == false)
try
vcmessage.setShapeType(Integer.parseInt(s));
catch(NumberFormatException nfe){}
if(haveOpeningShapePropertiesTag)
if(haveOpeningShapeLocationTag)
if(haveOpeningXCoordTag)
try
vcmessage.setXCoordinate(Integer.parseInt(s));
catch(NumberFormatException nfe){}
else if(haveOpeningYCoordTag)
try
vcmessage.setYCoordinate(Integer.parseInt(s));
//reset all flags for ShapeLocation, X and Y coordinates
haveOpeningXCoordTag = false;
haveOpeningYCoordTag = false;
//haveOpeningShapeLocationTag = false;
catch(NumberFormatException nfe){}
else if(haveOpeningBoundsTag)
if(haveBoundsWidth == false)
try
vcmessage.setBoundsWidth(Integer.parseInt(s));
catch(NumberFormatException nfe){}
else if(haveBoundsHeight == false)
try
vcmessage.setBoundsHeight(Integer.parseInt(s));
//reset flag
//haveOpeningBoundsTag = false;
catch(NumberFormatException nfe){}
else if(haveOpeningFGColorTag)
if(haveFGRed == false)
try
vcmessage.setFGRed(Integer.parseInt(s));
catch(NumberFormatException nfe){}
else if(haveFGGreen == false)
try
vcmessage.setFGGreen(Integer.parseInt(s));
catch(NumberFormatException nfe){}
else if(haveFGBlue == false)
try
vcmessage.setFGBlue(Integer.parseInt(s));
//reset flag
//haveOpeningFGColorTag = false;
catch(NumberFormatException nfe){}
else if(haveOpeningBGColorTag)
if(haveBGRed == false)
try
vcmessage.setBGRed(Integer.parseInt(s));
catch(NumberFormatException nfe){}
else if(haveBGGreen == false)
try
vcmessage.setBGGreen(Integer.parseInt(s));
catch(NumberFormatException nfe){}
else if(haveBGBlue == false)
{ System.out.println("getting BGBlue data");
try
vcmessage.setBGBlue(Integer.parseInt(s));
//reset flag
//haveOpeningBGColorTag = false;
catch(NumberFormatException nfe){}
else if(haveOpeningThicknessTag)
try
vcmessage.setThickness(Integer.parseInt(s));
catch(NumberFormatException nfe){}
else if(haveOpeningIsFilledTag)
vcmessage.setIsFilled(s);
else if(haveOpeningImageDataTag && vcmessage.getProcessEvent() == org.jcanvas.comm.ProcessEvent.MODIFY)
vcmessage.setBase64ImageData(s);
else if(haveOpeningTextDataTag && vcmessage.getProcessEvent() == org.jcanvas.comm.ProcessEvent.MODIFY)
vcmessage.setTextData(s);
//reset
haveOpeningShapePropertiesTag = false;
emit(s);
//===========================================================
// Utility Methods ...
//===========================================================
// Wrap I/O exceptions in SAX exceptions, to
// suit handler signature requirements
private void emit(String s)throws SAXException
try {
out.write(s);
out.flush();
} catch (IOException e) {
throw new SAXException("I/O error", e);
// Start a new line
private void nl()throws SAXException
try {
out.write(lineEnd);
} catch (IOException e) {
throw new SAXException("I/O error", e);
//treat validation errors as fatal
public void error(SAXParseException e)
throws SAXParseException
throw e;
// dump warnings too
public void warning(SAXParseException err)
throws SAXParseException
System.out.println("** Warning"
+ ", line " + err.getLineNumber()
+ ", uri " + err.getSystemId());
System.out.println(" " + err.getMessage());
}Just out of curiosity what happens if you append a space to the end of the XML document?
-
Dear Gurus,
Is there any report which will show the corresponding material document of 105 MVT/ 104 MVT type for 103 MVT type Material document
Regards,
RajeshHi,
What you have to do is:
Enter Tcode MB51...Enter Mvt type 103 and in to enter 105..
Now clcik on F8 Button...It will display you the result as per what you have expected..
Cheers!!
Utsav -
Settings for 103/105 movt type
I want to follow the route of 103 and 105 for import vendors and 101 for domestic vendors.
What are the settings that are to made for the 103 and 105 movement type and how can i control the same via vendor or Purchase order. That is system should not allow me to create a 101 for a import vendor and vice versa.
ThanksHi
There is no standard Configuration for this ...you need to use an user exit or BADI ....
BAdI - MB_CHECK_LINE_BADI can be used for this purpose....
But you need to different your Domestic & import PO;s using Document type.... Whcih can be used as the logic for determining which movment type to be used....
Please take help of your ABAPER in implmenting this
Thanks & Regards
Kishore -
Stock not updated after GR with 103 & 105 movement types
Hi All
I have raised one GR(MIGO) with ref to PO and movement type as 103(GR for PO with GR blocked stock).
The same was released in MIGO using movement type '105'and stock type selected 'Unrestricted use'.
After first step, In MMBE stock updated under 'GR Blocked Stock'.
But after second step no stock was updated in 'Unrestricted use'.
the actual scenario is:
The receipts from vendor for a PO need to be blocked and then later should go to unresticted use.
Can any body help me how to address this and Tcodes need to be used.
Regards
Nageswara...Hi GSC
Thanks for your reply and it is some what understandable.I have few more questions.
1.Is it possible to create PO with out Account and Costcenter not assigned. If so what is the impact.
2.My current settings were not allowing to create the PO with GL account and Costcenter.
M just confused with the "PO with account assignment" concept. Could you spare some time for this and help me to understand?
Thanks in advance
Nageswara... -
Goods Receipt 103/105 - CIN
Hi
we need to receive goods first with 103 movt type then 105
we don't have option capture & post excise in MIGO
It is need to be done separately using J1IEX
Please confirm the sequence of below steps
1. PO
2. J1IEX-Capture
3. MIGO 103 - refer excise
4. J1IEX-Post
5. MIGO 105
6. MIRO
RajuHI,
103 mvmt does not update ur inventory then how it is possible to POST?
PO,
MIGO -103 No Part 1
MIGO-105 PART-1
J1IEX-PART-2
Murugan -
Actually we have gate entry system (103 mvt ) during migo and make 105 mvt against the 103 material doc.
and also have restriction to make double entry against the same material doc (103).
In po the amount is let 100 qty , but how po allow to make 200 qty.
Kindly point out What is the cause for it and how to restrict it.
The above showing the Line item no 1500 Double GRN is made against 103 mvt type bypass error msg. and po qty.Yes Abhishek,
You are right i also agree with you , it is a standard sap , System never allow to change the error to
warning , i also tested in quality client it's ok. -
Hi Gurus,
In Purchase Order GR scenario, QM is active at M.Type 103 & Inspection Lot is generated. Once UD is done then with M. Type 105, material is sent to Unrestricted Use or Blocked Stock.
Now after 103 M. Type, system allowing to do M. Type 105 without Qualty results & lot approval. Is there anyway by which system should restrict 105 M.type unless Quality Check is done.Hi Pradeep,
One thing you can do is to create a status profile and assign it at the inspection type level or inspection lot level. In the status profile, create actions Quality check done and not done. Select actions UD forbidden and UD allowed for the object types Inspection lots. But one thing you need to remember that this has to be done manually. Initially the default can be set not to allow UD. And then you need to change the status to UD allowed.
This is one of the solution you can try.
Reward if useful and close the thread.
Keerthi
Maybe you are looking for
-
Why do I need Cellular Data turned on to send/receive MMS?
So after over 3 hours on the phone with Verizon, Apple, then Verizon again trying to figure out why I can't send or receive mms messages unless Cellular Data is on, doing a hundred soft/hard/network/every reset imaginable, a Verizon rep this morning
-
Upgrading of photo library from iphoto 8.1.2 to 9.6
I have had my photo library running on an external disk on my old iMac with iphoto 9 (8.1.2) running. I just bought a MacBook with iPhoto 9.6 installed. I wanted to switch my external disk to the MacBook, and when I did so I got prompted with: "The p
-
Can't import songs into itunes playlist folders from itunes music folder
Ive got to be an idiot. ive had my ipod for years and ive yet to figure this out: how do i put music into my playlist folders? The only playlists ive been able to successfully create and use are the ones ON my ipod. but that requires me to plug in my
-
Agreement ( Contract) is not coming up in SAP (VA42)
Agreement ( Contract) is not coming up in SAP (VA42)...How to troubleshoot...
-
Oracle 9ir2 Max length of element/field name?
Does anyone know what the max length of a element/field name can be in Oracle 9ir2? thanks, -mcd