Error in Importing Flat file by FDMEE
Hi,
I am trying to import a Flat File through FDMEE in a BSO Cube , but its throwing error at the import step only
Error in FileData.importData Traceback (most recent call last): File "<string>", line 39, in importData
RuntimeError: Exception in the file import servlet call
I am not using any import script , I am trying to import a simple flat file with a Rule to import it (Workflow->Data Load Rule).
Hi Sharad,
How did you rectify the issue mentioned:
Error in FileData.importData Traceback (most recent call last): File "<string>", line 39, in importData
RuntimeError: Exception in the file import servlet call
I am facing the same issue and would really appreciate if I can get any guidelines or related document on fixing this issue.
Please provide help on this at the earliest as this issue is affecting my deliverables.
Thanks,
Sumit Wadhwa
Similar Messages
-
Error: An error occurred importing the file. Detail: File does not exist or
Hi,
I am getting the error the below error while importing the file in FDM. I have read and write access to the folder. I tried loading text and excel files, I am getting the same error.
An error occurred importing the file.
Detail: File does not exist or access denied.
Thanks.Hi Tony,
Thanks for the reply.
I have Oracle Database and the version is 11.1.0.7; So even for this version do I need to have SQLLDR.exe on the server where FDM is installed.
Thanks,
Edited by: user10720012 on May 16, 2011 11:42 AM -
Error while importing .xml file in Datatype
Hi SDN,
I am getting this error while importing .xml file in Datatype.
Error when parsing the XML document (Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8
Actually I have created datatype in my development box..
but my client doesn't want to develop in development box.
so i have exported that datatype as xsd from datatype editor.
and while importing into sandbox datatype editor i am getting this error..
Any help please......Hi Rajeev,
now i have an .xml file its not importing into datatype...
error is
Error when parsing the XML document (Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8))
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema targetNamespace="http://abc.com/xa" xmlns="http://abc.com/xa" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:complexType name="DT_PLANNINGSCHEDULE">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">3c6ae480f2f111dbc7ac0002556ad065</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="PlanningSchedule_Output">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">c65d41c0f15b11dbb29f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PlanningScheduleHeader">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">c65d41c1f15b11dbb6ef00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ScheduleID" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">6c804600f15d11dbc02400123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ScheduleIssueDate" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a370c1d0f15d11db8dd800123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="SchedulePurpose">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a370c1d1f15d11dbac4100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Purpose">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1b4fd50f15e11db9eb600123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PurposeCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1b4fd51f15e11dbc47a00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ScheduleTypeCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a370c1d2f15d11dbbc3900123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ScheduleTypeCodedOther" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a370c1d3f15d11dba00200123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="QuantityQualifierCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a370c1d4f15d11dbc7e000123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ScheduleParty">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a370c1d5f15d11db969a00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="BuyerParty">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">449ec100f16411dba2e900123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Party">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">449ec101f16411db997a00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PartyID">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">449ec102f16411dbb75900123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Identifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">449ec103f16411db8fa500123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Agency">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">449ec104f16411dba93f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AgencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">449ec105f16411dba20f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Ident" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">0de2f450f16511dbaa4700123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ListOfIdentifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d0f16711dbbdd800123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Identifier" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d1f16711dbcd2600123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Agency">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d2f16711db82f800123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AgencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d3f16711dbcf6e00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Ident" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d4f16711dbcb6200123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="SellerParty">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">e0422b80f16711dba8c100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Party">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb80f16811db82e800123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PartyID">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb81f16811dba6ab00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Identifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb82f16811db8b4e00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Agency">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb83f16811dbc0ff00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AgencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb84f16811dbb8f700123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Ident" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb85f16811dba46200123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ListOfIdentifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb86f16811db98c000123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Identifier" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb87f16811dbb25200123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Agency">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb88f16811dbc7d100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AgencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">e99ffa30f16811dba27100123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Ident" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d30f16a11dbb29f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ShipFromParty">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">e0422b81f16711dbbfce00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Party">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d31f16a11db9adf00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PartyID">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d32f16a11dbbef100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Identifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d33f16a11db9e5600123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Agency">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d34f16a11dbba6d00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AgencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d35f16a11db855400123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Ident" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d36f16a11db877300123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ShipToParty">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">e0422b82f16711db84ec00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Party">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">275ecac0f16b11dba49600123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PartyID">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">275ecac1f16b11db80c700123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Identifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">275ecac2f16b11db8ea300123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Agency">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">275ecac3f16b11dbb5bb00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AgencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">275ecac4f16b11dbb7bc00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Ident" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">275ecac5f16b11db92a300123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Language">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a370c1d6f15d11db9f9a00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="LanguageCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1b4fd52f15e11dbc06300123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ListOfLocationGroupedPlanningDetail">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">c65d41c2f15b11dba9fd00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="LocationGroupedPlanningDetail" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">89515130f17f11db98e400123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Location">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">de832980f17f11db8d4600123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="LocationIdentifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">f95b26d0f18011db8ce800123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="LocID">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">f95b26d1f18011db839900123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Identifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">f95b26d2f18011dba45300123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Agency">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">f95b26d3f18011db9ac700123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AgencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">f95b26d4f18011dbc4ab00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Ident" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">f95b26d5f18011dbcd4400123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ListOfLocationPlanningItemDetail">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">de832981f17f11db856100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="LocationPlanningItemDetail">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257410f18111db8b6f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="BasePlanningDetail">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257411f18111db839c00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="LineItemNum">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257412f18111db847f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="BuyerLineItemNum" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257413f18111dbcf7200123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ItemIdentifiers">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257414f18111dba6f100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PartNumbers">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257415f18111db968700123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="BuyerPartNumber">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257416f18111db9f9100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PartNum">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257417f18111dbc32500123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PartID" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257418f18111dbcfa900123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="StandardPartNumber">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">50b67960f18211db839c00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ProductIdentifierCoded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">50b67961f18211dbc78900123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ProductIdentifierQualifierCoded" type="xsd:integer">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">50b67962f18211dbae6e00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ProductIdentifier" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">83815570f18411dbb4e800123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ItemDescription" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">83815571f18411db876f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ListOfItemReferences">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef0f18711dbbafe00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ListOfReferenceCoded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef1f18711db8a7600123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ReferenceCoded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef2f18711db935200123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ReferenceTypeCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef3f18711dba69c00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ReferenceTypeCodedOther" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef4f18711db942b00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="PrimaryReference">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef5f18711db93a800123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Reference">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef6f18711dbcebc00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="RefNum" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef7f18711dbce6300123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ForecastFrequencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef8f18711db937b00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ListOfScheduleDetail">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef9f18711dba61400123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ScheduleDetail">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aefaf18711db9d4800123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="CommitmentLevelCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aefbf18711dba59800123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ScheduleDates">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aefcf18711db947900123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ListOfDateCoded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aefdf18711dbc43e00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="DateCoded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aefef18711dbaa5000123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Date">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aefff18711dbcde600123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="DateQualifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59af00f18711db87f100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="DateQualifierCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59af01f18711dbc9cf00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ScheduleQuantities">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59af02f18711dbc24100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ListOfQuantityCoded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59af03f18711db842900123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="QuantityCoded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59af04f18711dbb59400123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="QuantityValue" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59af05f18711dba6d900123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="UnitOfMeasurement">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a87e2580f18711dbc66f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="UOMCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a87e2581f18711db89a000123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="QuantityQualifierCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a87e2582f18711db9a1500123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema> -
Error while importing swf file in to Crystal Xcelsius Designer 4.5
help me...., Error while importing swf file in to Crystal Xcelsius Designer 4.5
I read in the book called "CRYSTAL XCELSIUS for DUMMIES" on page 243 under topic called Nesting a Dashboard within another Dashboard.
sorry i used the wrong word embed, here i am importing the swf using image component.
My requirement is somethis like this parent child dependency menu.
eg: i have to two tabs 1)alphabets 2) Numerics First levet menu
if you click alphabets tab then the following menu A/B/C/D/..... Z i have diff charts.. under each alphabet.
If you click numberic tab then the follwing menu should one/two/three/.......ten here also i have diff charts under number
in over to avoid complexity in dynamic visibility i divided the into 3 dashboards. 1- alphabets 2- number and 3 -importing both swfs.. everything works fine except first tab and last tab under alphabets and numerics.
If some one help me with some alernative ... would be great.
Thanks -
Getting error while loading Flat File
Hello All,
I am getting error while loading flat file. Flat file is a CSV file.
Value ',,,,,,,,' of characteristic 0DATE is not a number with 000008 spaces
Data seprator |
Escape sign ;
It has 23708 entries , it s loading successfully till 23 665 entries
Besides when checked in PSA
for record having entries >23667 has calender day as ,,,,,, where as rest entries are having date
Besides when i checked in Flat file ,the total number of rows is 23,667 is there but i wonder why it has got 23,708 in
RSMO
Could you please let me know how to correct.
regards
pathHi,
For date column you should maintain YYYYMMDD formate Eg: 20090601, kepp cursor on date column and right click and Formate >Custome>make it 00000000 then save teh file as .CSV . First type values on column and do like this formate and save it and without opening it load it. Once you open it you losw 00000000 formate you need to give again the same formate.
Settings in Infopackage:
Data Format = CSV
Data Separator = ,
Escape Sign = ;
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/01ed2fe3811a77e10000000a422035/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/80/1a6567e07211d2acb80000e829fbfe/content.htm
Thanks
Reddy -
Error while importing zip file for second time to B2B through ant script
[echo] args=import
importstatus:
[echo] Commandline arguments 1: [import]
[echo] Import with overwrite=true
[echo] B2BCommandLineUtility: importRepository: Error messages:
[echo] MDS-00521: error while reading document /soa/b2b/tpa_JOvrtiV-7030143
019445112136.xml from metadata repository
[echo] MDS-00520: failure to read document /soa/b2b/tpa_JOvrtiV-70301430194
45112136.xml because it is not in the metadata repository
[echo] MDS-00911: Document with name "/soa/b2b/tpa_JOvrtiV-7030143019445112
136.xml" and version 16 does not exist in the repository.
[echo] ORA-01403: no data found
[echo] ORA-06512: at "DEV_MDS.MDS_INTERNAL_SHREDDED", line 407
[echo] ORA-06512: at "DEV_MDS.MDS_INTERNAL_SHREDDED", line 603
[echo] ORA-06512: at line 1
[echo]
[echo] ORA-01403: no data found
[echo] ORA-06512: at "DEV_MDS.MDS_INTERNAL_SHREDDED", line 407
[echo] ORA-06512: at "DEV_MDS.MDS_INTERNAL_SHREDDED", line 603
[echo] ORA-06512: at line 1
[echo]
[echo] ORA-01403: no data found
[echo] ORA-06512: at "DEV_MDS.MDS_INTERNAL_SHREDDED", line 407
[echo] ORA-06512: at "DEV_MDS.MDS_INTERNAL_SHREDDED", line 603
[echo] ORA-06512: at line 1
[echo]
[echo]
Can anybody plz help???
Thanks in Advance!!!Hi,
Even I am getting the same error while importing the .zip file for the second time through B2B console-->Administration-->Import/export tab.
But again it works for the third time..
Error Message:
Import of file OriginalProject.zip failed. MDS-00521: error while reading document /soa/b2b/tpa_MnjhBHh-70301432125893445241.xml from metadata repository MDS-00520: failure to read document /soa/b2b/tpa_MnjhBHh-70301432125893445241.xml because it is not in the metadata repository MDS-00911: Document with name "/soa/b2b/tpa_MnjhBHh-70301432125893445241.xml" and version 34 does not exist in the repository. ORA-01403: no data found ORA-06512: at "DEV_MDS.MDS_INTERNAL_SHREDDED", line 407 ORA-06512: at "DEV_MDS.MDS_INTERNAL_SHREDDED", line 603 ORA-06512: at line 1 ORA-01403: no data found ORA-06512: at "DEV_MDS.MDS_INTERNAL_SHREDDED", line 407 ORA-06512: at "DEV_MDS.MDS_INTERNAL_SHREDDED", line 603 ORA-06512: at line 1 ORA-01403: no data found ORA-06512: at "DEV_MDS.MDS_INTERNAL_SHREDDED", line 407 ORA-06512: at "DEV_MDS.MDS_INTERNAL_SHREDDED", line 603 ORA-06512: at line 1
Please help... -
Error while Importing MDL File
Hi All,
While Importing a MDL File, I am getting the following Error. Can someone help me asap.
mport started at Apr 6, 2010 10:20:09 AM
Project "PUBLIC_PROJECT"
Error occurred importing from file "C:\oracle\product\10.2.0\db_2\owb\bin\admin\ETLDEV-20100405_2210.mdl".
oracle.wh.util.Assert: Repository Connection Error: The connection to the repository was lost, because of the following database error: Closed Connection Exit OWB without committing.
at oracle.wh.util.Assert.owbAssert(Assert.java:51)
at oracle.wh.ui.common.UIExceptionHandler.handle(UIExceptionHandler.java:186)
at oracle.wh.ui.common.UIExceptionHandler.handle(UIExceptionHandler.java:156)
at oracle.wh.ui.common.UIExceptionHandler.handle(UIExceptionHandler.java:152)
at oracle.wh.util.SQLExceptionHandler.handle(SQLExceptionHandler.java:65)
at oracle.wh.repos.pdl.lock.OracleLock.release(OracleLock.java:153)
at oracle.wh.repos.pdl.lock.OracleLockOptimizer.unlock(OracleLockOptimizer.java:138)
at oracle.wh.repos.pdl.lock.LockOperation.execute(LockOperation.java:90)
at oracle.wh.repos.pdl.lock.LockOperationSet.execute(LockOperationSet.java:51)
at oracle.wh.repos.pdl.lock.LockMaster.downgradeToExclude(LockMaster.java:222)
at oracle.wh.repos.pdl.lock.LockMaster.destroyLockHolder(LockMaster.java:199)
at oracle.wh.repos.pdl.lock.RequestToHolderMap.endRequest(RequestToHolderMap.java:83)
at oracle.wh.repos.pdl.lock.RequestToHolderMap.closeFolderForCreate(RequestToHolderMap.java:39)
at oracle.wh.repos.pdl.lock.LockModuleImpl.closeFolderForCreate(LockModuleImpl.java:61)
at oracle.wh.repos.pdl.dispatcher.EventDispatcherImpl.closeFolderForCreate(EventDispatcherImpl.java:174)
at oracle.wh.repos.pdl.metadataloader.Import.MDLLockManager.releaseMDLImportLocks(MDLLockManager.java:456)
at oracle.wh.repos.pdl.metadataloader.Import.MDLImport.releaseImportLocks(MDLImport.java:1531)
at oracle.wh.repos.pdl.metadataloader.Import.MDLImport.process(MDLImport.java:1981)
at oracle.wh.repos.pdl.metadataloader.Import.MDLRunImport.internalRunImport(MDLRunImport.java:431)
at oracle.wh.repos.pdl.metadataloader.Import.MDLRunImport.runImport(MDLRunImport.java:503)
at oracle.wh.ui.metadataloader.Import.MDLUpgradeImportTransaction.internalRunImport(MDLUpgradeImportTransaction.java:218)
at oracle.wh.ui.metadataloader.Import.MDLUpgradeImportTransaction.run(MDLUpgradeImportTransaction.java:319)
Thanks,
SMDid the instance go down whilst doing this?
Is there more to the log before where you started it?
Cheers
David -
Error in InfoPackage: Error when uploading Flat Files
Hello Experts,
I encoutered this error in Info Package when uploading a flat file.
When i try to click on the "Preview" button, this errors appear:
"Error 8 when compiling the upload program: Row
237, message: Data Type / BIC/ CCCBMA1_COCTR2 was found in a newer"
Please help to advise what is this error about and how to resolve this?hi Annie,
run RSA1 and try again
Error when compiling the upload program (Message no. RSAR233)
other similar problem solved by run program(SE38)RS_TRANSTRU_ACTIVATE_ALL and relogon
A newer version of the data type error when loading
Flat File Preview error message
Error when loading from Flat File
Error message when previewing data in InfoPackage
hope this helps. -
An error occured importing the file
Hello,
We are currently experiencing an issue with Importing a file that contains the Japanese Kanji character set.
The error received is "Error - An error occured importing the file"
The Kanji characters are only for the Descriptions within the import file and WILL NOT be stored in the Oracle Database. I have enabled the East Asian lanaguages on the Windows 2k3 server but still get the error. Is there another setting the needs to be enabled or a 3rd party software that must be installed?
Any help would be appreciated.
Thanks
TonyHello,
It appears that you did not tell FDM to accept possible non ASCII characters.
To do this change the option in "Administration" -> "Configuration Settings" -> "File Encoding Type" to Unicode.
Keep in mind this will allow the parsing engine to accomidate additional characters. BUT, if the file is an ANSI type file that contains the characters and not a TRUE Unicode file, the characters will just now be skipped.
Thank you. -
Hi all
Can any one please tell me , how to import flat files from 'postgres database' on a completely different network?
Thank YouAre you wanting to unload to file from Postgres? Or use ODBC connectivity to it? ODBC would allow remote connectivity using the database gateway connectivity. Running an unload on postgres instance to file and ftp'ing the file is another option.
Cheers
David -
I want to import flat files by ftp in owb
I want to import flat files by ftp in owb.
When I config the ftp host ip, username, password and path, then I import the flat files, but
this didn't succeed. And I find the owb didn't check the ftp host's directory,
and it check the localhost of owb, so it reported there isn't the directory.
So how to solve the problem.
Thank you!Hi,
you must first transfer the files via ftp to the dbserver and then process. Create a workflow with a ftp activity and transfer the files. After this you can call the mappings in this workflow.
If you want to sample the flat files you have two choices:
1.) Using the owb client on the dbserver and sample the files on the dbserver. Then you need only one location with the path on the db-server.
2.) Using the owb client on a client machine and sample the files on the client. Then you need two locations: one local which points to the file directory on your client, one remote which points to the path on the dbserver. Use the first to sample the files, and change to the second before deploying the mappings.
Regards,
Detlef -
An error occurred importing the file, although some of the file data may ha
I am trying to update some xml. I login to admin module and click on Import Exchange File. When I try to import an xml I get this error:
An error occurred importing the file, although some of the file data may have been processed. ==> com.waveset.util.IOException: ==> java.sql.SQLException: ORA-01407: cannot update ("WAVESET_V60_QA"."OBJECT"."XML") to NULL
I have checked database permission and the user has proper permission.
Any idea why I would get this error?
Thank you in advance
DevalHi,
source account must have values. If not, check your import format.
Regards -
How to import flat file as a source in DAC Client
Dear All,
I am doing some R&D,I have a problem that how can i import the flat file in DAC client which i am using as a source.
Can any one please explain in detail step wise.
Regards
Tarang JainHi Tarang,
How long will it take to run the sample execution plan? Since when i run 'CRM Automotive' EP, it runs for more than 3 hours and still it is running. My system config is 1GB RAM with windows os. I have also opened the DAC server and client in console mode and I m not able to see any errors. I have only got only the task 'Load row into run table ' completed successfully and next 10 are in Running stage from the past 2 hours.
My DAC client shows continously the below shown message for 1 hr.
'Sep 30, 2008 3:52:59 PM com.siebel.analytics.etl.client.data.model.ConnectionHan
dler getConnection
INFO: Getting connection for: Model structure for W_ETL_RUN_STEP (RUN_STEP) (cur
rently 0)
Sep 30, 2008 3:52:59 PM com.siebel.analytics.etl.client.data.model.ResultSetPars
er logMinutesSeconds
INFO: Query took 0 minutes, 0 seconds
Sep 30, 2008 3:52:59 PM com.siebel.analytics.etl.client.data.model.ConnectionHan
dler cleanUp
INFO: Returning connection for: Model structure for W_ETL_RUN_STEP (RUN_STEP) (c
urrently 1)
Sep 30, 2008 3:52:59 PM com.siebel.analytics.etl.client.data.model.ResultSetPars
er logMinutesSeconds
INFO: Populating DACObjects took 0 minutes, 0 seconds
Sep 30, 2008 3:52:59 PM com.siebel.analytics.etl.client.data.model.DACChildTable
Model setParentID
INFO: PARENT ROW ID IS: 95D45F88DBB268B3D19DB71B4E42D3FF
Sep 30, 2008 3:52:59 PM com.siebel.analytics.etl.client.data.objectcomponents.Mo
delStruct setQuery
INFO: SELECT
RUN_STEP.DEPTH
,RUN_STEP.STEP_NAME
,RUN_STEP.STATUS
,RUN_STEP.START_TS
,RUN_STEP.END_TS
,RUN_STEP.STATUS_DESC
,RUN_STEP.PHY_SRC_NAME
,RUN_STEP.PHY_TRGT_NAME
,RUN_STEP.PHY_FOLDER_NAME
,RUN_STEP.SERVER_NAME
,RUN_STEP.PHASE_NAME
,RUN_STEP.EXEC_TYPE_NAME
,RUN_STEP.SUCESS_ROWS
,RUN_STEP.FAILED_ROWS
,RUN_STEP.ERROR_CODE
,RUN_STEP.DEFN_STEP_WID
,RUN_STEP.ROW_WID
,RUN_STEP.LAST_UPD
,RUN_STEP.APP_WID
,RUN_STEP.RUN_WID
,RUN_STEP.STEP_WID
,RUN_STEP.PHY_SRC_WID
,RUN_STEP.PHY_TRGT_WID
,RUN_STEP.PHY_FOLDER_WID
,A_W_ETL_APP.ROW_WID
,A_W_ETL_APP.NAME
FROM W_ETL_RUN_STEP RUN_STEP
INNER JOIN W_ETL_APP A_W_ETL_APP ON RUN_STEP.APP_WID=A_W_ETL_APP.ROW_WID
WHERE
(RUN_STEP.RUN_WID='95D45F88DBB268B3D19DB71B4E42D3FF')
ORDER BY
RUN_STEP.START_TS ASC,
RUN_STEP.DEPTH ASC'
Any comments on this?
I had also copied the CRM Analytics source file into the "D:\Informatica\PowerCenter8.1.1\server\infa_shared\SrcFiles"
as metioned in Appendices ' Configuring Universal Adapter for CRM Analytics'.
With Regards,
Prads -
How to capture errors records in flat file in BDC
hi ,
i would like to know how to capture error records while uploading a flat file to screen through BDC .
appreciatable solutions are rewarded.
thanks,
shanHi shan,
write this code, it will solve your problem.
DATA : BDCTAB LIKE BDCDATA OCCURS 0 WITH HEADER LINE.
DATA : I_MSG LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
DATA : BEGIN OF I_ERR OCCURS 0,
MATNR(18),
FLAG(1),
MSG(100),
END OF I_ERR.
DATA :V_LINES TYPE I.
LOOP AT ITAB.
REFRESH BDCTAB.
PERFORM SCREEN USING: 'SAPLMGMM' '0060'.
PERFORM FIELD USING: 'RMMG1-MATNR' ITAB-MATNR,
'RMMG1-MBRSH' ITAB-MBRSH ,
'RMMG1-MTART' ITAB-MTART,
'BDC_OKCODE' '/00'.
PERFORM SCREEN USING: 'SAPLMGMM' '0070'.
PERFORM FIELD USING: 'MSICHTAUSW-KZSEL(01)' 'X' ,
'MSICHTAUSW-KZSEL(02)' 'X' ,
'MSICHTAUSW-KZSEL(09)' 'X' ,
'BDC_OKCODE' '=ENTR'.
PERFORM SCREEN USING: 'SAPLMGMM' '0080'.
PERFORM FIELD USING: 'RMMG1-WERKS' ITAB-WERKS,
'BDC_OKCODE' '=ENTR'.
PERFORM SCREEN USING: 'SAPLMGMM' '4004'.
PERFORM FIELD USING: 'MAKT-MAKTX' ITAB-MAKTX,
'MARA-MEINS' 'EA' ,
'MARA-MATKL' '001',
'BDC_OKCODE' '/00'.
PERFORM SCREEN USING: 'SAPLMGMM' '4004'.
PERFORM FIELD USING: 'BDC_OKCODE' '/00'.
PERFORM SCREEN USING: 'SAPLMGMM' '4000'.
PERFORM FIELD USING: 'MAKT-MAKTX' ITAB-MAKTX,
'MARA-MEINS' 'EA',
'MARC-EKGRP' '001',
'MARA-MATKL' '001',
'BDC_OKCODE' '=BU'.
CALL TRANSACTION 'MM01' USING BDCTAB
MODE 'A'
MESSAGES INTO I_MSG.
FINDING LAST MESSAGE IN THE I_MSG TABLE*****
DESCRIBE TABLE I_MSG LINES V_LINES.
ACCORDING TO THE V_LINES NUMBER TABLE WILL BE READ****
READ TABLE I_MSG INDEX V_LINES.
CALL FUNCTION 'FORMAT_MESSAGE'
EXPORTING
ID = I_MSG-MSGID
LANG = '-D'
NO = I_MSG-MSGNR
V1 = I_MSG-MSGV1
V2 = I_MSG-MSGV2
V3 = I_MSG-MSGV3
V4 = I_MSG-MSGV4
IMPORTING
MSG = I_ERR-MSG
EXCEPTIONS
NOT_FOUND = 1
OTHERS = 2
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
IF I_MSG-MSGID EQ 'M3' AND I_MSG-MSGNR EQ '800'.
I_ERR-FLAG = 'S'.
ELSE.
I_ERR-FLAG = 'E'.
ENDIF.
I_ERR-MATNR = ITAB-MATNR.
APPEND I_ERR.
CLEAR I_ERR.
ENDLOOP.
WRITE:/ 'SUCCESS RECORDS' COLOR COL_POSITIVE.
SKIP.
WRITE:/ 'MATERIAL' COLOR COL_HEADING, 20 'MESSAGE' COLOR COL_HEADING.
LOOP AT I_ERR WHERE FLAG EQ 'S'.
WRITE:/ I_ERR-MATNR, 20 I_ERR-MSG.
ENDLOOP.
SKIP 2.
WRITE:/ 'ERROR RECORDS' COLOR COL_NEGATIVE.
SKIP.
WRITE:/ 'MATERIAL' COLOR COL_HEADING, 20 'MESSAGE' COLOR COL_HEADING.
LOOP AT I_ERR WHERE FLAG EQ 'E'.
WRITE:/ I_ERR-MATNR, 20 I_ERR-MSG.
ENDLOOP.
*& Form SCREEN
SCREEN
form SCREEN using P_PROG P_SCREEN.
BDCTAB-PROGRAM = P_PROG.
BDCTAB-DYNPRO = P_SCREEN.
BDCTAB-DYNBEGIN = 'X'.
APPEND BDCTAB.
CLEAR BDCTAB.
endform. " SCREEN
*& Form FIELD
FIELD
form FIELD using FNAME FVAL .
BDCTAB-FNAM = FNAME.
BDCTAB-FVAL = FVAL.
APPEND BDCTAB.
CLEAR BDCTAB.
endform. " FIELD
Thanks,
Murali -
Error while importing PAR file from local system.
Hi Experts,
While importing PAR file into my NWDS, I am encountered by some strange error.
Please refer below screenshot for your reference.
After clicking on "OK" button of the above error popup, another popup emerge with different error, please find below the screenshot for this error.
Please let me know the reason and resolution of this error. It will be very helpful for me.
Thanks in advance.
Thanks and Regards,
sarvesh AgarwalHi ,
Are u trying to import with .bak extension ? If so please rename the file and remove .bak extension and try.
x.par is enough to import not x.par.bak.
Thanks,
Maybe you are looking for
-
Dump in BAPI while fetching data
Hi all, I m getting a short dump (: ' No more storage space available for extending an internal table.') in my vendor trial balance report . The place of short dump is the BAPI which im using to fetch opening balance i.e BAPI_AP_ACC_GETKEYDATEBALANC
-
Path problem when moving from Mac to PC
Adobenoob wrote: Hi, I'm trying to move our Adobe InDesign installation from Mac to PC, but I ran into a path problem. A lot of our publications/documents in Adobe InDesign have linked to pictures in the filesystem (Windows 2008 R2 server). It goes l
-
I have a WRE54G Range Expander that is currently operating in a wireless mode over an encrypted network. The signal is very weak. so what i want to do is to run an ethernet cable from the router to the WRE54G Range Expander which would allow me to mo
-
Am using direct input method. i want to provide user with* Selection Screen* where user will enter Material No. i have to check whether that material present in MARA table or not. If that material not present there error message or proceed with LSMW
-
Dear Guru, When i am trying to creating an order but when i am go to order cost there cost analysis is empty i dont what happen there?When i am going to progress confirmation co1f i got below errors:- 1.error determing actual cost