IMPORTANT:
this is not a Support Forum! Experienced users might answer from time to time questions posted here. If you need a professional and reliable answer, or if you want to report a bug, please contact Altova Support instead.

Profile: rahulkhanna
About
User Name: rahulkhanna
Forum Rank: Newbie
Real Name:
Location India
Occupation:
Interests:
Gender: None Specified
Statistics
Joined: Wednesday, February 18, 2015
Last Visit: Thursday, July 30, 2015 11:45:36 AM
Number of Posts: 3
[0.02% of all post / 0.00 posts per day]
Avatar
Last 10 Posts
Topic: Problem regarding the Advance Positional mapping
Posted: Thursday, July 2, 2015 12:19:17 PM
vlad wrote:
You can use the new functionality with Regular expression for Repeated split so that 00, 10, 50, 60, 99 remain on the same level


Can you please tell me from where to do it, I do not see an Regular Expression for Repeated Split. I am using Altova enterprise Expression 2015, sp2,x64.
Topic: Problem regarding the Advance Positional mapping
Posted: Tuesday, June 30, 2015 2:14:39 PM
Problem regarding the Advance Positional mapping


Users- we are facing one unique problem of Advance Positional Schema. According to requirement, I need to create APS which will be a fixed length schema.
I need to do mapping of 13 rows with as follows.
00
10
20 (child of 10)
21 (child of 10)
30 (child of 10)
40 (child of 10)
41 (child of 10)
41 (child of 10)
50
60
99

In this schema 00, 10, 50, 60, 99 are parallel to each other whereas 20, 21, 30, 40, 41 are child of 10 and are parallel to each other.
The problem what I am facing is while doing a repeated split against a file each and every segment is becoming child of former. For eg. 10 becoming child of 00, 20 becoming child of 10, 21 becoming child of 20 and so on.

I need to know if there is any way in Altova wherein I can make my schema as per requirement. I am also attaching schema file and test file of what I am doing.

File Attachment(s):
pos.mft (5kb) : <Rahul Khanna> This the schema file
SC_820_218_Hop2_TGLICAP.txt <Rahul Khanna> This file contains the information about the fixed length of all rows.
Payment-mft.mfd <Rahul Khanna> This the mfd file which is finally created after using the pos.mft.
TGLICA_RI_X12_820_218_2015-08-05_08-20-51_1.xml <Rahul Khanna> XML file for the source.
Payment Schema-1.1.0.xsd <Rahul Khanna> Schema file for .mfd file for the source.
Test file.txt (8kb) <Rahul Khanna> This is test file or the expected output file that is expected from the mfd file created by using the mft file.

To see what is the length of an element do below. For eg I am taking first 2 elements of 00 row

00,E820_E820_ISA_ST_CD,E820_E820_ISA_ST_CD,string,,,1,2,L,F <This has start from 1 and will go till 2, so length is 2>
00,E820_ISA13_INTCHG_CNTL_NUM,E820_ISA13_INTCHG_CNTL_NUM,string,,,3,11,L,F <This has start from 3 and will go till 11, so length is 8> and so on.

Please let me know in case any more information is needed and in case there is ambiguity in my explanation.

Any guidance will be fine.

Topic: Multiple ST in a GS Loop
Posted: Wednesday, February 18, 2015 8:21:01 PM
Team- I am facing one very peculiar issue for which I need a immediate reply if somebody can for mapping.

While working I was creating GS based upon one tag. Now what is happening is multiple ST segments are getting created in one GS which is wrong.

Can anyone help me what error I might be doing. See below for example :

GS*BE*HCX*22444PA0040018*20150127*075602*2113*X*005010X220A1~
ST*834*1111*005010X220A1~
BGN*00*1*20150127*075602*ES***2~
DTP*303*D8*20150201~
QTY*TO*2~
QTY*DT*1~
QTY*ET*1~
N1*P5*HCENTIVE*FI*123456789~
N1*IN*HAP*XV*382242827~
N1*BO*broker hap*94*121~
ACT*5555555555~
INS*N*G8*021*EC*A****N*N~
REF*0F*0000007776~
REF*17*0000007858~
REF*6O*01232015I000548~
DTP*356*D8*20150201~
NM1*IL*1*ghjghj*nghj~
PER*IP**TE*4322342342*EM*newhorizon@mail.com~
N3*sdfert*retet~
N4*crt*PA*18017**CY*NORTHAMPTON~
DMG*D8*20150117*F~
HLH*N~
HD*021**HLT~
DTP*348*D8*20150201~
DTP*349*D8*20160201~
REF*CE*22444PA0040018~
REF*1L*000007550~
LS*2700~
LX*1~
N1*75*PRE AMT 1~
REF*9X*110.75~
DTP*007*D8*20150201~
LX*2~
N1*75*SOURCE EXCHANGE ID~
REF*17*HCX~
DTP*007*D8*20150201~
LX*3~
N1*75*REQUEST SUBMIT TIMESTAMP~
REF*17*20150127075556~
DTP*007*D8*20150201~
LX*4~
N1*75*SEP REASON~
REF*17*03~
DTP*007*RD8*20150114-20150129~
LE*2700~
INS*Y*18*021*EC*A***AC*N*N~
REF*0F*0000007776~
REF*17*0000007776~
REF*6O*01232015I000548~
DTP*356*D8*20150201~
NM1*IL*1*horizon*new****34*789797897~
PER*IP**TE*4322342342*EM*newhorizon@mail.com~
N3*sdfert*retet~
N4*crt*PA*18017**CY*NORTHAMPTON~
DMG*D8*19810102*M*I~
HLH*N~
HD*021**HLT~
DTP*348*D8*20150201~
DTP*349*D8*20160201~
DTP*300*D8*20150123~
REF*CE*22444PA0040018~
REF*1L*000007550~
LS*2700~
LX*1~
N1*75*PRE AMT 1~
REF*9X*211.73~
DTP*007*D8*20150201~
LX*2~
N1*75*RATING AREA~
REF*9X*R-PA006~
DTP*007*D8*20150201~
LX*3~
N1*75*PRE AMT TOT~
REF*9X*787.04~
DTP*007*D8*20150201~
LX*4~
N1*75*SOURCE EXCHANGE ID~
REF*17*HCX~
DTP*007*D8*20150201~
LX*5~
N1*75*REQUEST SUBMIT TIMESTAMP~
REF*17*20150127075556~
DTP*007*D8*20150201~
LX*6~
N1*75*ADDL MAINT REASON~
REF*17*CONFIRM~
DTP*007*D8*20150201~
LX*7~
N1*75*SEP REASON~
REF*17*03~
DTP*007*RD8*20150114-20150129~
LE*2700~
SE*92*1111~
ST*834*1113*005010X220A1~
BGN*00*1*20150127*075602*ES***2~
DTP*303*D8*20150201~
QTY*TO*2~
QTY*DT*1~
QTY*ET*1~
N1*P5*HCENTIVE*FI*123456789~
N1*IN*HAP*XV*382242827~
N1*BO*broker hap*94*121~
ACT*5555555555~
INS*N*G8*021*EC*A****N*N~
REF*0F*0000007776~
REF*17*0000007858~
REF*6O*01232015I000548~

Use of the Altova User Forum(s) is governed by the Altova Terms of Use.