SMLT -- Czech Language Import -- .PAT files
Dear Support,
We are planning to import/add a new Czech Language into our ECC 60 system.
When I called the SMLT transaction to import the language from FrontEnd, the system is not finding the content from the CD 51033496_1. The CD has .PAT files instead of .sar or .car files.
I have also copied the .PAT file onto /usr/sap/trans/EPS/in, but still the SMLT tool is not finding the language content to import.
Could you please help me out with this issue?
Thank you,
Nikee
HI Nikee
check this SAP Nope , hope this will solve ur issue
Note 1254022 - SMLT: Language imports not displayed in EHP systems
SMLT displays only the languages for which the current (SAP Basis) release has been imported. This makes sense because otherwise, the system would also display the language imports for the previous release after an upgrade. The problem now occurs because the systems that have an Enhancement Package imported the same language packages as the systems that do not have an Enhancement Package even though the release is different. For example, the SAP Basis 7.00 language package is imported into an SAP Basis 7.01 system. Since the releases do not correspond, the system does not display the language package in SMLT.To correct the error, SMLT must recognize an Enhancement Package release and the release check for this must be configured in a more flexible way
Cheers
dEE
Similar Messages
-
Hi,
I'm trying to import the French language into a 4.6c R/3 IDES training system. In transaction SMLT during the import process i'm having an issue with the path for the language packages. How do i point this to Front End Cd drive? Whatever path I put in there, it returns with an error, "Specify a valid path". I've tried copying the files to the local SAP server in a directory, for example to C:\lang and entering this into the path, but still have no sucess.
According to this : -
http://help.sap.com/saphelp_nw2004s/helpdata/EN/a3/30ad5296b511d384bb0060975b04f3/content.htm
There should be an option to "Load from Front End", this I don't have to can't see.
Thanks for your help!Hi Tin,
check below things
Before you start transaction SMLT for language import, you must configure the required languages using the RSCPINST report. For more information, see SAP Note 42305.
In SMLT, the names of the imported language packages are only displayed with up to 12 characters. Therefore, language packages with longer names (up to 20 characters) are truncated.
Also check
http://help.sap.com/erp2005_ehp_02/helpdata/EN/21/5532d395ea11d384bb0060975b04f3/content.htm
Regards
Ashok -
Copying of PAT file..
Dear SAP Guru's,
how to copy the PAT file to Z.PAT file...
here we want to copy the language fiel(>PAT ) file Z and store into one request..so please can any one help me out how to do the convertion the .PAT file to Z .PAT file..
Here we have one SAP NOTE: 981731.
Thanks and Regards,
GSANAthanks keerthi,,
what i did, first i pasted pat file in trans/eps/in. now i used transaction saint . it said to click on continue... and i did...
some process is going on screen...
pls give me a b c of it....
regards.
Edited by: chinta on Dec 1, 2011 7:31 AM -
Language Import Error using Transaction SMLT - STRALAN_MSAG 075
Hi ,
My current client required Chinese Language - ZH (Chinese Simplified) in ECC 6.0 SR3 Unicode System
As per procedure, i have added chinese language 'ZH' using i18n -> i18n Customising -> i18n System Configuration menu.
Later in Transaction 'SMLT', i tried to add the language pack "ZHECC63F.PAT" by pasting & importing from EPS/in folder. The Import is getting terminated stating "Incorrect package format".
Kindly let me know what is the correct format. I have pasted the "ZHECC63F.PAT" file from the Language Installation DVD (51033496) delivered by SAP with license order.
SM37 gives the below message
Date Time Message text Message class Message no. Message ty
06.11.2008 17:06:56 Job started 00 516 S
06.11.2008 17:06:56 Step 001 started (program RSTLAN_IMPORT, variant &0000000000000, user ID KPITBASIS) 00 550 S
06.11.2008 17:06:56 Application log IHBD9Cot09hX08002aGV2W STRALAN_MSAG 109 I
06.11.2008 17:06:56 Restart import (state:lc_disassemble) STRALAN_MSAG 103 I
06.11.2008 17:06:56 ... system date: 06.11.2008 system time: 17:06:56 STRALAN_MSAG 363 I
06.11.2008 17:06:57 Step DISASSEMBLE ... STRALAN_MSAG 050 I
06.11.2008 17:06:57 ... system date: 06.11.2008 system time: 17:06:57 STRALAN_MSAG 363 I
06.11.2008 17:06:57 ... do not overwrite data files and cofiles (settings) STRALAN_MSAG 095 I
06.11.2008 17:06:57 Incorrect package format STRALAN_MSAG 075 E
06.11.2008 17:06:57 Job cancelled after system exception ERROR_MESSAGE 00 564 A
Action Log from SMLT givesbelow error
Start import (state:initial)
... system date: 06.11.2008 system time: 16:42:51
Version: 700.F.15
Step INIT ...
... system date: 06.11.2008 system time: 16:42:51
... configuration "Selective Language Import"
... executed successfully
Step DISASSEMBLE ...
... system date: 06.11.2008 system time: 16:42:52
... do not overwrite data files and cofiles (settings)
Incorrect package format
Restart import (state:lc_disassemble)
... system date: 06.11.2008 system time: 16:50:24
Step DISASSEMBLE ...
... system date: 06.11.2008 system time: 16:50:24
... do not overwrite data files and cofiles (settings)
Incorrect package format
Rgds
Ganesh.SHello Ganesh,
You need to restart the import by cancelling it and restarting it again from SMLT.
Just cancel the current import! And we would need to reimport the same with the correct patches!
Following OSS notes would provide you further insights:
Note 830722 - Current note for language transports in Release 7.0
Note 195442 - Language import and Support Packages
Note 48047 - Mode of operation of report RSREFILL
Thank You,
Antarpreet -
Data files removed during language import
Hi,
While running a language import on ECC 6.0, someone removed the data files from the /usr/sap/trans/data directory.
We are facing 2 problems now :
1. the language that must be imported is now locked in SMLT (no lock exists in SM12 as described in help)
2. we can't find how to recreate the datafile from the .PAT file located on the install DVD. (some people have told me they did it before, but can't find back how)
Can someone please help ?
Tx in advance
Patrice.What I know is,
If the datafiles deleted we can't add manually. better to install. before that taka a backup of existing one.
regards
ganesh -
Error in Language import using SMLT .
Hi,
I was importing japanese language in SAP ERP 6.0 EHP4. import process was started using SMLT and the import process is taking long to get imported.
Below is the observation in SMLT:
1. JOB: SAP-LANGUAGE-IMP JA SAPKLJASR1EH shows status finished.
2. Action log is stuck at:
@5B\QInformation@ Start import (state:initial)
@5B\QInformation@ ... system date: 10.09.2014 system time: 12:40:58
@5B\QInformation@ Version: 701.F.15
@5B\QInformation@ Step INIT ...
@5B\QInformation@ ... system date: 10.09.2014 system time: 12:40:58
@5B\QInformation@ ... configuration "Selective Language Import"
@5B\QInformation@ ... executed successfully
@5B\QInformation@ Step DISASSEMBLE ...
@5B\QInformation@ ... system date: 10.09.2014 system time: 12:40:59
@5B\QInformation@ ... do not overwrite data files and cofiles (settings)
@5B\QInformation@ ... executed successfully
@5B\QInformation@ Step ADD TO BUFFER ...
@5B\QInformation@ ... system date: 10.09.2014 system time: 12:42:22
@5B\QInformation@ ... executed successfully
@5B\QInformation@ Step MAIN IMPORT ...
@5B\QInformation@ ... system date: 10.09.2014 system time: 12:42:28
@5B\QInformation@ ... number of parallel import processes: 1 (settings)
@5B\QInformation@ ... start tp IMPORT SUBSET (TPSTAT = 20140910124228390)
@5B\QInformation@ ... waiting for entry in TPSTAT (12:42:28)
@5B\QInformation@ ====== Control passed to tp/R3trans (see long text) ======
3. At OS level, location: E:\usr\sap\trans\log and file: SLOG1437.RE1 shows the following message:
START imp single RE1 20140910123924 BASIS mb3ap1024 20140910124228390
START DD IMPORT RE1 H 20140910123925 BASIS mb3ap1024 20140910124228390
WARNING: System RE1. Warning. 20140910124154 :
ERROR: The following call returned with exit code 7:
ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=RE1
ERROR: Background jobs cannot be started.
ERROR: Please check trace file dev_evt.
WARNING: (This warning is harmless if no further warnings follow.)
WARNING: System RE1. Warning. 20140910124755 :
ERROR: The following call returned with exit code 7:
ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=RE1
ERROR: Background jobs cannot be started.
ERROR: Please check trace file dev_evt.
WARNING: (This warning is harmless if no further warnings follow.)
WARNING: System RE1. Warning. 20140910125155 :
ERROR: The following call returned with exit code 7:
ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=RE1
ERROR: Background jobs cannot be started.
ERROR: Please check trace file dev_evt.
WARNING: (This warning is harmless if no further warnings follow.)
WARNING: System RE1. Warning. 20140910125255 :
WARNING: Background job RDDIMPDP could not be started or terminated abnormally.
Please check that the R/3 system is running.
Please check the system. Use transactions SM21, SM37, SM50.
WARNING: (This warning is harmless if no further warnings follow.)
WARNING: System RE1. Warning. 20140910125556 :
ERROR: The following call returned with exit code 7:
ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=RE1
ERROR: Background jobs cannot be started.
ERROR: Please check trace file dev_evt.
WARNING: (This warning is harmless if no further warnings follow.)
WARNING: System RE1. Warning. 20140910130156 :
ERROR: The following call returned with exit code 7:
ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=RE1
ERROR: Background jobs cannot be started.
ERROR: Please check trace file dev_evt.
WARNING: (This warning is harmless if no further warnings follow.)
WARNING: System RE1. Warning. 20140910130557 :
ERROR: The following call returned with exit code 7:
ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=RE1
ERROR: Background jobs cannot be started.
ERROR: Please check trace file dev_evt.
WARNING: (This warning is harmless if no further warnings follow.)
WARNING: System RE1. Warning. 20140910130657 :
WARNING: Background job RDDIMPDP could not be started or terminated abnormally.
Please check that the R/3 system is running.
Please check the system. Use transactions SM21, SM37, SM50.
WARNING: (This warning is harmless if no further warnings follow.)
i tried abortimp and started the import again but the error messages were the same as first time.
Kindly provide some assistance on this issue.
Regards,
Mamta Bijlani.WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F1.RE1
is already in use (170), I'm waiting 3 sec (20140910144553). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F1.RE1
is already in use (180), I'm waiting 4 sec (20140910144622). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F1.RE1
is already in use (190), I'm waiting 5 sec (20140910144658). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F2.RE1
is already in use (10), I'm waiting 1 sec (20140910145640). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F2.RE1
is already in use (20), I'm waiting 2 sec (20140910145703). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F2.RE1
is already in use (30), I'm waiting 3 sec (20140910145734). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F2.RE1
is already in use (40), I'm waiting 4 sec (20140910145804). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F2.RE1
is already in use (50), I'm waiting 1 sec (20140910145836). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F2.RE1
is already in use (60), I'm waiting 2 sec (20140910145858). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F2.RE1
is already in use (70), I'm waiting 5 sec (20140910145929). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F2.RE1
is already in use (80), I'm waiting 4 sec (20140910150002). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F2.RE1
is already in use (90), I'm waiting 3 sec (20140910150039). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F2.RE1
is already in use (100), I'm waiting 2 sec (20140910150109). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F2.RE1
is already in use (110), I'm waiting 3 sec (20140910150142). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F2.RE1
is already in use (120), I'm waiting 5 sec (20140910150208). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F2.RE1
is already in use (130), I'm waiting 3 sec (20140910150234). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F2.RE1
is already in use (140), I'm waiting 4 sec (20140910150312). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F2.RE1
is already in use (150), I'm waiting 4 sec (20140910150349). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (10), I'm waiting 4 sec (20140910151604). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (20), I'm waiting 1 sec (20140910151635). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (30), I'm waiting 2 sec (20140910151706). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (40), I'm waiting 1 sec (20140910151731). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (50), I'm waiting 3 sec (20140910151804). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (60), I'm waiting 1 sec (20140910151828). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (70), I'm waiting 1 sec (20140910151855). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (80), I'm waiting 5 sec (20140910151929). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (90), I'm waiting 5 sec (20140910151958). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (100), I'm waiting 4 sec (20140910152024). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (110), I'm waiting 2 sec (20140910152105). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (120), I'm waiting 1 sec (20140910152133). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (130), I'm waiting 1 sec (20140910152157). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (140), I'm waiting 4 sec (20140910152234). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (150), I'm waiting 2 sec (20140910152308). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (160), I'm waiting 5 sec (20140910152341). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (170), I'm waiting 4 sec (20140910152419). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (180), I'm waiting 4 sec (20140910152450). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (190), I'm waiting 4 sec (20140910152516). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (200), I'm waiting 1 sec (20140910152544). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (210), I'm waiting 2 sec (20140910152614). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (220), I'm waiting 5 sec (20140910152636). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (230), I'm waiting 4 sec (20140910152715). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (240), I'm waiting 1 sec (20140910152749). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (250), I'm waiting 3 sec (20140910152820). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (260), I'm waiting 2 sec (20140910152854). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (270), I'm waiting 5 sec (20140910152932). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (280), I'm waiting 5 sec (20140910152959). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (290), I'm waiting 1 sec (20140910153025). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (300), I'm waiting 4 sec (20140910153055). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (310), I'm waiting 4 sec (20140910153123). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (320), I'm waiting 3 sec (20140910153156). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (330), I'm waiting 2 sec (20140910153230). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (340), I'm waiting 4 sec (20140910153259). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (350), I'm waiting 4 sec (20140910153326). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (360), I'm waiting 4 sec (20140910153353). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (370), I'm waiting 2 sec (20140910153430). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (380), I'm waiting 1 sec (20140910153456). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (390), I'm waiting 1 sec (20140910153526). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (400), I'm waiting 2 sec (20140910153548). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (410), I'm waiting 3 sec (20140910153615). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (420), I'm waiting 2 sec (20140910153649). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (430), I'm waiting 4 sec (20140910153716). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (440), I'm waiting 1 sec (20140910153748). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (450), I'm waiting 4 sec (20140910153812). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (460), I'm waiting 2 sec (20140910153845). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (470), I'm waiting 5 sec (20140910153917). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (480), I'm waiting 5 sec (20140910153951). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (490), I'm waiting 3 sec (20140910154022). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (500), I'm waiting 1 sec (20140910154051). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (510), I'm waiting 5 sec (20140910154120). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (520), I'm waiting 5 sec (20140910154151). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (530), I'm waiting 5 sec (20140910154223). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (540), I'm waiting 2 sec (20140910154255). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (550), I'm waiting 2 sec (20140910154327). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (560), I'm waiting 5 sec (20140910154358). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (570), I'm waiting 3 sec (20140910154426). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (580), I'm waiting 1 sec (20140910154455). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (590), I'm waiting 4 sec (20140910154525). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (600), I'm waiting 4 sec (20140910154600). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (610), I'm waiting 5 sec (20140910154634). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (620), I'm waiting 4 sec (20140910154710). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (630), I'm waiting 2 sec (20140910154741). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (640), I'm waiting 4 sec (20140910154801). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (650), I'm waiting 2 sec (20140910154830). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (660), I'm waiting 4 sec (20140910154909). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (670), I'm waiting 5 sec (20140910154935). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (680), I'm waiting 4 sec (20140910155007). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (690), I'm waiting 3 sec (20140910155045). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (700), I'm waiting 3 sec (20140910155117). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (710), I'm waiting 3 sec (20140910155149). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (720), I'm waiting 5 sec (20140910155222). My name: pid 6896
on mb3ap1024 (APServiceRE1)
WARNING: \\MB3AP1020\sapmnt\trans\tmp\SAPKKLJASR1EHP4ERP6F4.RE1
is already in use (730), I'm waiting 1 sec (20140910155254). My name: pid 6896
on mb3ap1024 (APServiceRE1)
SLOG 50 lines. -
Language Attribute Error while creating PAT files using SSDC & SSDA
When trying to create the .pat file(Add-On package creation) with AAK 4.0 tool.
Error of language attribute at the time of register the delivery in SSDA.
When finally try to register the created package it gives error message :
"Package can not be registered. Check the attributes"
Please suggest possible resolution.Hello
We will get this error message when we run this from application other than "Time and Labor Engine". So try to run this concurrent program (if you registered as a conc. program) from Time and Labor Engine application.
--Lokesh -
Dear All,
I have a requirement to install the Arabic language. I am trying in IDES first(ECC 6) and the steps which I follow ,
1. Copy the file ARNW04S2.PAT from the DVD ( 2004 SR2 ) and put it in /usr/sap/trans/EPS/in folder.
2 . Went to SMLT and Classify Language, select Arabic and supplementary as English.
3. So now I could see Arabic in the main screen of SMLT. and then select Arabic --> Import Package
Language Arabic
Path /usr/sap/trans/EPS/in
SAPKLAR700SR2NW04SF0 Language NetWeaver 2004s SR2 AR 24.08.2006
and setting it was the Current Client ( 000).
4. The import of packages was successful now and I could see in the SMLT the Arabic languages> imported Packages> SAPKLAR700SR2NW04SF0 and green status.
5. Now when I do Language> Special Action> Import Support Packages and then see Support Packages found in system and some list of Status description like
Must be imported ( highlighted)
Translation already exists for this Support Package
Now if I enter it another screen comes with Step: Search for Existing Files at the Operating System Level
and waiting for Path for CAR Archives and description like
Not Found
I am stuck at this step and when I press Enter
Reduce the list to all found packages, or specify the paths
to the CAR/SAPCAR archives.
even if I give the path /usr/sap/trans/EPS/in .. the same thing happens.
Is there any other steps to do????
Also in instance profile the zcsa/inst... is AR.The step
Choose Language u2192 Special Actions u2192 Import Support Packages.
is remaining from my side as I could not go ahead. Lots of message as already discribed.
Any solution to it???
Now I am trying to download the SP from servicemarket place. Can anybody suggest me which to download as per the error message in SMLT> Spl Action> Import SP
Translation already exists for this Support ( so shld I download the SP for it?
and
Must be imported( so I need to download the SP for it). It has all very big list of all the SAP components. Should I need to download for everything??
Language not in package. Language not necessary. SAPK-60001INFINBASIS Financial Basis Support Package 01 for Release 600
There are lots of this now,
14 Translation already exists for this Support Package SAPKW70003 BW Support Package 03 for 7.00
15 Must be imported SAPK-60001INECCDIMP Object list for ECC-DIMP 600 SP01
16 Must be imported SAPK-60001INFICA Object list for FI-CA 600 SP01
17 Must be imported SAPK-60001INFICAX Object list for FI-CAX 600 SP01
18 Must be imported SAPK-60001ININSURANC Object list for INSURANCE 600 SP01
19 Must be imported SAPK-60001INISCWM Object list for IS-CWM 600 SP01
20 Must be imported SAPK-60001INISH object list for IS-H 600 SP01
21 Must be imported SAPK-60001INISM object list for IS-M 600 SP01
22 Must be imported SAPK-60001INISOIL object list for IS-OIL 600 SP01
23 Must be imported SAPK-60001INISPSCA object list for IS-PS-CS 600 SP01
24 Must be imported SAPK-60001INISUT object list for IS-UT 600 SP01
25 Must be imported SAPKE60001 object list for SAP_HR 600 SP01
26 Must be imported SAPKGPAD01 object list for EA-APPL 600 SP01
27 Must be imported SAPKGPDD01 object list for EA-DFPS 600 SP01
28 Must be imported SAPKGPFD01 object list for EA-FINSERV 600 SP01
29 Must be imported SAPKGPGD01 object list for EA-GLTRADE 600 SP01
Language not in package. Language not necessary. SAPK-60001INFINBASIS Financial Basis Support Package 01 for Release 600
Language not in package. Language not necessary. SAPK-60001INERECRUIT ERECRUIT 600: patch 0001
Language not in package. Language not necessary. SAPKGS6001 SEM-BW Support Package 01 for Release 600
Language not in package. Language not necessary. SAPK-60001INLSOFE LSOFE 600: patch 0001
Language not in package. Language not necessary. SAPKIBHDA0 LC Applications (LCAPPS) 2005_700
Language not in package. Language not necessary. SAPK-700U7INSAPSLL SLL-LEG 700 : Add-On Supplement
Language not in package. Language not necessary. SAPK-200UDINWFMCORE WFMCORE 200 Upgrade: Meta-Commandfile (Delta Task)
Language not in package. Language not necessary. SAPK-200UFINWFMCORE WFMCORE 200 Upgrade: Meta-Commandfile (Delta Task)
Language not in package. Language not necessary. SAPK-200UOINWFMCORE WFMCORE 200 Upgrade: Meta-Commandfile (Delta Task)
Language not in package. Language not necessary. SAPK-200URINWFMCORE WFMCORE 200 Upgrade: Meta-Commandfile (Delta Task)
Language not in package. Language not necessary. SAPK-200UKINWFMCORE WFMCORE 200 Upgrade: Meta-Commandfile (Delta Task)
Language not in package. Language not necessary. SAPK-200UMINWFMCORE WFMCORE 200 Upgrade: Meta-Commandfile (Delta Task)
Edited by: Basis Ad on Sep 29, 2008 3:06 PM
I am trying to get the SP from service marketplace for eg. for FI_CA as suggested in the message, but its a note
HTM SAPK-60001INFICA SP 01 for FI-CA 6.00 Info 3 24.10.2005
So downloading it will it make sense?
Edited by: Basis Ad on Sep 29, 2008 3:15 PM -
.PAT file format?
Are there docs anywhere that describe the .PAT patterns file format?
I'm trying to get to the pixels that are used for a pattern that are used in a "pattern overaly" effect. I don't think any of the Suites give this info.
Thanks in advance :-)Hello Ganesh,
You need to restart the import by cancelling it and restarting it again from SMLT.
Just cancel the current import! And we would need to reimport the same with the correct patches!
Following OSS notes would provide you further insights:
Note 830722 - Current note for language transports in Release 7.0
Note 195442 - Language import and Support Packages
Note 48047 - Mode of operation of report RSREFILL
Thank You,
Antarpreet -
Language Import Supplementation
Hi
I am importing a new language (French) into our NW04 ECC 5 system, we already use English and German which are standard.
1) I plan to import the language from the .PAT file into client 000 using SMLT
2) Import previously imported Support packs for the language
3) Supplement French with English for missing texts into the Production client 100
Should I also supplement French with English in client 000 ?
Thanks.Hello ecnirp,
Yes u should supplement the language in each client since its client specific
http://help.sap.com/saphelp_nw2004s/helpdata/en/37/3e3d38b611b065e10000009b38f889/content.htm
regards,
Anand -
Problem with Language Import (could not create cofile)
Hi everybody
I'm trying to load the language pack "Spanish", but falls and gives me the following message
"could not create cofile"
Somebody could give me some indication on how to overcome this mistake, I've seen out there and some queries, but I have not overcome my problem!
I have created the "Transport System" and charged the language in "DEV Server," but I can not bring it to "test" if the attempt to import "TCode SMLT" gives me the error above.
thanksthis is action log!
@5B\QInformation@ Start import (state:initial)
@5B\QInformation@ ... system date: 23.08.2008 system time: 16:38:07
@5B\QInformation@ Version: 700.F.15
@5B\QInformation@ Step INIT ...
@5B\QInformation@ ... system date: 23.08.2008 system time: 16:38:07
@5B\QInformation@ ... configuration "Selective Language Import"
@5B\QInformation@ ... executed successfully
@5B\QInformation@ Step DISASSEMBLE ...
@5B\QInformation@ ... system date: 23.08.2008 system time: 16:38:07
@5B\QInformation@ ... do not overwrite data files and cofiles (settings)
@5C\QError@ Could not create cofile
@5B\QInformation@ Restart import (state:lc_disassemble)
@5B\QInformation@ ... system date: 23.08.2008 system time: 16:46:21
@5B\QInformation@ Step DISASSEMBLE ...
@5B\QInformation@ ... system date: 23.08.2008 system time: 16:46:21
@5B\QInformation@ ... do not overwrite data files and cofiles (settings)
@5C\QError@ Could not create cofile
@5B\QInformation@ Restart import (state:lc_disassemble)
@5B\QInformation@ ... system date: 23.08.2008 system time: 17:05:01
@5B\QInformation@ Step DISASSEMBLE ...
@5B\QInformation@ ... system date: 23.08.2008 system time: 17:05:01
@5B\QInformation@ ... do not overwrite data files and cofiles (settings)
@5C\QError@ Could not create cofile
Test in STMS
RFC connections Ok
Connection Test Ok
Transport Tool Ok
Transport Directory Ok
Check Transport Directory 24.08.2008 18:49:28
ECP System ECP
Transport Directory
bin
mts-sap\sapmnt\trans\bin
buffer
mts-sap\sapmnt\trans\buffer
cofiles
mts-sap\sapmnt\trans\cofiles
data
mts-sap\sapmnt\trans\data
log
mts-sap\sapmnt\trans\log
sapnames
mts-sap\sapmnt\trans\sapnames
tmp
mts-sap\sapmnt\trans\tmp -
Language Import broken and locked
Hello,
during the language import, the process is for some reason broken. But when I tried to start it again, but it says "Language locked, you cant perform this action".
In "SM12", I didn't find any lock entry. In one SAP note (1064502), it is said to delete something from table "TPSTAT". But I don't what should be deleted.
Any help is appriciated. Thank you very much.
Rongfeng
P.S.
Possible Broken Reason:
1. inside SLOG0810.PFQ:
ERROR: /usr/sap/trans_PFP/log/SAPILZFN17.PFQ : cant open
: No space left on device
2. another reason could be:
the language file system is over mounted. I umount one time during the import.Hello,
Please go to transaction SMLT and simply enter "abortimp" in the transaction field and press enter. It will unlock the import.
You can now import again.
Best regards,
Olivier -
Error Importing text file (FDM Error 53)
When Importing a file, I receive the error "Unable to locate file" with the error logged as below. I am not using any custom import scripts and the adapter has been registered correctly.
Any thoughts?
** Begin FDM Runtime Error Log Entry [2011-03-03 10:22:09] **
ERROR:
Code............................................. 53
Description...................................... File not found
Procedure........................................ clsUtilities.fShellAndWait
Component........................................ upsWDataWindowDM
Version.......................................... 1112
Thread........................................... 4888
IDENTIFICATION:
User............................................. omarcassim
Computer Name.................................... STJH1076
App Name......................................... FDMUAT
Client App....................................... WebClient
CONNECTION:
Provider......................................... ORAOLEDB.ORACLE
Data Server......................................
Database Name.................................... HYPUAT1
Trusted Connect.................................. False
Connect Status.. Connection Open
GLOBALS:
Location......................................... FMS_TO_HFM
Location ID...................................... 752
Location Seg..................................... 6
Category......................................... ACTUALS
Category ID...................................... 12
Period........................................... Dec - 2010
Period ID........................................ 12/31/2010
POV Local........................................ False
Language......................................... 1033
User Level....................................... 1
All Partitions................................... False
Is Auditor....................................... False
** Begin FDM Runtime Error Log Entry [2011-03-03 10:22:09] **
ERROR:
Code............................................. 53
Description...................................... File not found
Procedure........................................ clsImpDataPump.fImportTextFile
Component........................................ upsWObjectsDM
Version.......................................... 1112
Thread........................................... 4888
IDENTIFICATION:
User............................................. omarcassim
Computer Name.................................... STJH1076
App Name......................................... FDMUAT
Client App....................................... WebClient
CONNECTION:
Provider......................................... ORAOLEDB.ORACLE
Data Server......................................
Database Name.................................... HYPUAT1
Trusted Connect.................................. False
Connect Status.. Connection Open
GLOBALS:
Location......................................... FMS_TO_HFM
Location ID...................................... 752
Location Seg..................................... 6
Category......................................... ACTUALS
Category ID...................................... 12
Period........................................... Dec - 2010
Period ID........................................ 12/31/2010
POV Local........................................ False
Language......................................... 1033
User Level....................................... 1
All Partitions................................... False
Is Auditor....................................... False
** Begin FDM Runtime Error Log Entry [2011-03-03 10:22:09] **
ERROR:
Code............................................. 53
Description...................................... File not found
Procedure........................................ clsImpProcessMgr.fLoadAndProcessFile
Component........................................ upsWObjectsDM
Version.......................................... 1112
Thread........................................... 4888
IDENTIFICATION:
User............................................. omarcassim
Computer Name.................................... STJH1076
App Name......................................... FDMUAT
Client App....................................... WebClient
CONNECTION:
Provider......................................... ORAOLEDB.ORACLE
Data Server......................................
Database Name.................................... HYPUAT1
Trusted Connect.................................. False
Connect Status.. Connection Open
GLOBALS:
Location......................................... FMS_TO_HFM
Location ID...................................... 752
Location Seg..................................... 6
Category......................................... ACTUALS
Category ID...................................... 12
Period........................................... Dec - 2010
Period ID........................................ 12/31/2010
POV Local........................................ False
Language......................................... 1033
User Level....................................... 1
All Partitions................................... False
Is Auditor....................................... FalseI don't make use of an Oracle back end; however, if he is doing a SQL 'bulk insert' load type where he needs to pass the file, he probably needs to double check the path he used for the application assuming the database server is not the same as the FDM server.
i.e. App Path of C:\Hyperion\FDM\FDMApps\Blah\
Wouldn't work so good if Oracle DB is just passed a file path/name to import similar to MS SQL. Might need something like:
\\<FDM Server>\FDMApps\Blah\ -
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> -
Hi all,
In the Notepad, I created an xml file (ZenQroducts.xml) :
<Qroducts>
<Qroduct>
<SKU>1</SKU>
<Desc>Book</Desc>
</Qroduct>
<Qroduct>
<SKU>2</SKU>
<Desc>DVD</Desc>
</Qroduct>
<Qroduct>
<SKU>3</SKU>
<Desc>Video</Desc>
</Qroduct>
In my SQL Server 2012 Management Studio, I executed the following code:
--to create a new object Qroducts in a new database OPENXMLtesting
CREATE DATABASE OPENXMLtesting
GO
CREATE TABLE Qroducts(
sku INT Primary KEY,
qroduct_desc VARCHAR(30));
INSERT INTO Qroducts (sku, qroduct_desc)
SELECT X.qroduct.query('SKU').value('.', 'INT'),
X.qroduct.query('Desc').value('.', 'VARCHAR(30)')
FROM (
SELECT CAST(x AS XML)
FROM OPENROWSET(
BULK 'H:\ZenQroducts.xml',
SINGLE_BLOB) AS T(x)
) AS T(x)
CROSS APPLY x.nodes('Qroducts/Qroduct') AS X(qroduct);
SELECT sku, qroduct_desc
FROM Qroducts;
I got the following message:
Msg 9400, Level 16, State 1, Line 6
XML parsing: line 13, character 12, unexpected end of input
I have no ideas why I got this "XML parsing:line 13, character12, unexpected end of input" message. Please kindly help, advise me on where I made mistake and how I can resolve this problem, and respond in this Forum.
Thanks in advance,
Scott Chang
Hi Manish, Thanks for your response.
Yes, it is a duplicate with Qroducts/Qroduct instead of Products/Product. I did it, because I don't know how to remove the existing "Products" database.
Again, I got the existing "Qroducts" database in this second trial!!?? I am comletely lost in doing "Importing XML file to SQL Table" now!! I think that I have not touched T-SQL and XML programming, since 2008. I
did not catch the new features of T-SQL 2008, XML, SQL/XML, XQuery, etc. for long time. Recently, I did not know what DECLARE, @x, SET,...were, and dived into the SQL/XML and XQuery programming. I knew the SQL Basics (SELECT, FROM, WHERE,..), creating
the names of databases and tables in SQL Server 2008/2012 Management Studio (Express) before. This morning, I found an old T-SQL 2008 Prgrammer's Guide that has the new features of SQL Server 2008 for T-SQL, XML, XQuery, etc. I just starting reading
it to know what DECLARE, @x, SET,... are. But, I still don't know where the existing databases "Products" and "Qroducts" (created by me) are - they are not in the Databases of SQL Server 2012 Management Studio I am using!!?? Could
you please kindly point out where the "Products" and "Qroducts" databases are?
Prashanth responded to my posted question too and he asked to to try his code: DECLARE @xml XML, SELECT @xml =' <Qroducts>.....SELECT product.value.....FROM @XML.nodes.....AS.... I just learned that his code is doing the thing we
want to do and print the results below the SQL Query. This is not what I need in doing my SQL/XML programming. I am reading/studying the new (2008) features of T-SQL, XQuery 1.0: An XML Query Language (Second Edition), and Microsoft XQuery Language Reference
(SQL Server 2012 Books Online) closely now. I hope that I can resume the T-SQL, XML Query, SQL/XML, XQuery in my SQL Server 2012 Management Studio soon.
Please tell me where the existing databases "Products" and "Qroducts" I created in my previous trials in my SQL Server 2012 Management Studio. This is what I need to know and to delete them, before I do this kind of "Importing
XML file to Table of SQL Server 2012 Management Studio" programming again.
Please kindly help, advise and respond again.
Many Thanks,
Scott Chang
Maybe you are looking for
-
Why Does 3G Not Work on my IPhone
Apologies everyone - I am a real numpty with my IPhone. I have switched just about everything on i think I need to to enable 3G and my service provider says that in my present location the wireless service is excellent. So why is that on my top too
-
Hello to all. I've been googling around for days to find some examples to solve my problem but was unable to find a good one. I'm using Excel 2007 and Visual Studio 2010 Normally I report the data using Excel itself (a workbook). Now the request I ha
-
Hi Hussein, Unfortunately appsweb.cfg file under $ORACLE_CONFIG_HOME/forms/server/ is deleted.Now forms are not open. How can i re-create the appsweb.cfg file. Plz help me
-
Coloring data symbols in scatter graphs
Having created a scatter graph with 10 data points I would like to color each point differently. Does anyone know if you can do this? The complete data series can be colored, so ALL data points can be formatted but I cannot see how each point can be
-
Hi all!! I have this requeriment; Im using a WAD, and the user fill the variables for a range of dates; then the user can be save a view from the query and use it later. The view is saved with the values that the user fill in the variables; is possib