EDI 856 HL Looping


my sample edi files

hl*1**s*1~
ref*bm*bol1001~    -- bolnumber
dtm*011*20090205*145500~
n1*sf*testwh*9*1234567891234~  shipfrom wh name
n1*st*testwhanni - 62*9*0123456789123~
n1*vn*wm.inc.*9*9898989880000~
n1*by*abcinc*9*0069652140000~
hl*2*1*o*1~
prf*po1***20090205~   --- ponumber


i mapping edi xml data ...

below expectd output xml schema structure. 
<header>
<bolnumber>bol1001<\bolnumber>
<ponumber >po1 <ponumber >
<shipfrom> testwh <shipfrom>
</header>

problem hl looping

i tried map of options gives results

<header>  ---hl1
<bolnumber>bol1001<\bolnumber>
<shipfrom> testwh <shipfrom>
</header>
</header> ----hl2
<ponumber >po1 <ponumber >
<header>

hl looping ... header(xml schema)  with hl -1 ad hl-2 ....

how can avoided ? .. want in map without using custom xslt option.


thanks,
pankaj

pankaj

there several options might work you.

1.  have tried using value mapping (flattening) functoid in combination logical functoids?
2.  have tried using cumulative concatenate functoid in combination logical functoids.

else happening in map?  extracting above information can not separated other mapping, else may impact way engine behaves here.  looping functoids used output other hl levels, example, may cause problems here in header.

there several examples of how handle hl looping problems (including full chapter on 856) in pro mapping biztalk server 2009.

hope helps,
jim -- pro mapping in biztalk 2009, apress books, march 23, 2009


BizTalk Server  >  BizTalk Server EDI and AS2



Comments

Post a Comment

Popular posts from this blog

Azure DocumentDB Owner resource does not exist

having same error microsoft.azure.documents.documentclientexception: message: {"errors":["owner resource not exist"]} , scenario. when deployed webapp azure , try document docdb throws error. docdb exists in azure , contains document looking for. weird local machine(running vs) works fine. i'm using same settings in azure , local. have , idea this. thanks Microsoft Azure  >  Azure Cosmos DB
Read more

job syspolicy_purge_history job fail in sqlserver 2008

Image
hello guys, when installed sqlserver,it automatically created 1 job name job syspolicy_purge_history. but failed @ step 1. the reason is: date                11/6/2010 2:00:00 am log                job history (syspolicy_purge_history) step id                1 server                mxosv-otsdb01 job name                syspolicy_purge_history step name                verify automation enabled. duration                00:00:00 sql severity                16 sql message id                34022 operator emailed                operator net sent                operator paged                retries attempted                0 message executed user: nt authority\system. policy automation turned off. [sqlstate 42000] (error 34022).  the step failed. have run statement: select msdb.dbo.fn_syspolicy_is_automation_enabled the returned valus 0. what can resolve it? or can delete job manually.   thanks in advance. if haven't things want,be
Read more

Trying to register with public marketplace error with 'Get-AzureStackStampInformation'

when trying register against public azure adfs azure stack error below. logs can found at: c:\maslogs\azurestack.azureregistration.2017-10-12.01-31-23.log  and  \\azs-ercs01\c$\maslogs error occurred checking stamp information: system.management.automation.remoteexception: term 'get-azurestackstampinformation' not recognized name of cmdlet, function, script file, or operable program. check spelling of name, or if path included, verify path correct , try again. @ c:\azurestack-tools-master\registration\registerwithazure.psm1:1106 char:5 +     throw "logs can found at: $global:azureregistrationlog  and  \ ... +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + categoryinfo          : operationstopped: (logs can fou... , try again.:string) [], runtimeexception     + fullyqualifiederrorid : logs can found at: c:\maslogs\azurestack.azureregistration.2017-10-12.01-31-23.log  a    nd  \\azs-ercs01\c$\maslogs error occurred chec
Read more