Edi-help

hi,
can any one tell whats the difference between we02,we05,we07.
also i need wat are the most important transaction in edi and ale.
thank

Hi,
Basically WE02 and WE05 are same in terms of Functionality. Displays the Idocs. But there is one diff. one of these transaction is for Adminitration purpose.
And WE07 is for Error statistics. It displays the Idocs which went into errors. It classifies the idocs in there error types.
ALE IDOC
Main transaction is WEDI. From here u can do all the activities related to ALE and IDE.
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
Rgds,
Prakash

Similar Messages

PI EDI help: What is the source of ISA13 in a IDOC to EDI mapping

Hello Experts,
It would be of great help if you can provide the field mapping for ISA 13 in outbound from IDOC sceanrio:
IDOC: INVOIC02 - to - EDI 810 mapping.
Is it the best practice to have ECC send the value in a particular IDOC field ( like RFINT) or PI has to use a custom function to populate the ISA13 field.?
Thank you,
Patrick.

Hi,
ISA13 is for Interchange Control Number. It is a control number assigned by the interchange sender.
Normally its Sequential number starting with 000000001 and incremented by 1 for each subsequent ISA between sender and receiver.
This is a very useful value to include. It creates an explicit link between the IDoc and the EDI transmission. This number eases Production Support greatly. When there's an issue with a Partner EDI transmission, the Partner's EDI support people want to know the Interchange Control Number
The IDoc interface does not process or check this field.
regards
Ganga

EDI help please

Hello,
Can anybody please provide any links related to EDI 856, 810, and 820? We need to configure them in our system and want to find out the steps involved. Thanks in advance.

Hi...
EDI 214 & 856
Reg 856 fallout
EDI from legacy systems......
What is meant by ASN and importance of ASN
edi 856 inbound
Multi-mapping for EDI 810 Interface
EDI 810
Mapping from PEXR2002 iDoc to EDI 820
EDI 820 to Vendors
EDI 820
EDI 820/812 program?
Hope it helps you...
Reward points if useful......
Suresh.......

EDI help pls

can anyone help me with some gd EDI material pls

hey hemanth,
here r some links
check these links.....
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.onestopsap.com/interview-Question/ale/
http://www.onestopsap.com/interview-Question/edi/
http://www.allsaplinks.com/idoc_sample.html
http://www.sap-img.com/abap/ale-bapi.htm
http://www.sap-img.com/basis/difference-between-edi-and-idoc.htm
http://www.sappro.com/downloads/OneClientDistribution.pdf
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
Please check this link for EDI/ALE/IDoc online documentation.
http://www.easymarketplace.de/online-pdfs.php
If u find it useful mark the points
Regards,
Naveen

EDI IDOC generation for interface with Vendor software help needed.

EDI IDOC help needed.
We are NOT an EDI shop, but have a project to output data to Sales Force.com
Sales Force requests IDOC output - eg. 810 Outbound Invoice.
We will need to do a historical load of Orders/Quotes/Invoices from the past 2 years.
Is there a function module or series of FM's that are used to generate the E2EDKxxxxx type segments?
I have been testing using the IDOC_OUTPUT_INVOIC and IDOC_OUTPUT_ORDRSP FM's, but they generate segments begining with E1EDKxxxxx.
Basicall we have a report program that the user enteres in the date range of Order/Quotes/Invoices they wish to extract, the the program needs to output a flat file (.txt) on the server which is then picked up by Sales Force.com.
Also, is there a way to have in the Partner Profile a generic Partner under the "Type KU" that can be used for all orders/invoices so I don't have to create a KU Partner Type for each and every Sold-To customer we have?
I am very new to EDI so any help would be greatly appreciated.
Thanks.
Scott.

Hi Scott,
We will need to do a historical load of Orders/Quotes/Invoices from the past 2 years.
I know it's very tempting to use an interface for such loads if you anyhow have to create one. However, often the volume alone speaks against interface usage for such scenarios.
Is there a function module or series of FM's that are used to generate the E2EDKxxxxx type segments? I have been testing using the IDOC_OUTPUT_INVOIC and IDOC_OUTPUT_ORDRSP FM's, but they generate segments begining with E1EDKxxxxx.
Well, the E2* segments basically reflect the external name of the IDoc segment, whereas the function modules you're referring to basically just create an internal version of the IDoc. Once the IDoc framework then passes the IDocs to the partner, the segment names usually (depends on how the IDocs are passed on) get converted to their external name. If there are multiple versions of a segment, then the version number will be appended to the segment name.
Note that IDoc segment definitions are only partially stored in the data dictionary. If you want to see all versions you should always use transaction WE31 to look at segments. There you can also see for example for E1EDK01 the several versions and when you then use in SE37 function module SEGMENT_EXTERNAL_NAME_GET you will see what SAP produces as the external name for segment E1EDK01. This function module is basically the one that handles the segment name translations.
Ignore the comments for subsystem, this is basically an option in SAP to possibly trigger further external tools (e.g. mapping etc.) for handling the outbound IDocs.
Again, the funny thing is that via the WE30 transaction, if i put in INVOIC02 as the Obj. name and see the segments, i can see that E2EDK01 there is a version 005, but if i go to SE11 and put in E2EDK01005 structure line and i get a "not found". We just have up to E2EDK01002.
In the old days SAP used to generate E1, E2 and E3* structures in the data dictionary (SE11). The E1* structure reflected the character type representation of an IDoc segment, whereas the other two (definition and documentation) contained actual references to data elements (e.g. if you used a quantity field). However, in newer releases those dictionary structures (E2* & E3*) are no longer generated, because they're superfluous (meta data defined via WE31 is sufficient).
Cheers, harald

Tax with the help of idoc and EDI

Dear gurus,
how can we process tax data that is used between two systems through the help of IDOC and EdI? It would be great for ur kind support.

Hi Amit,
I do not understand how a non-sap system having an idoc adapte?
Do you mean the non-sap system has the ability to understand the IDOC files?
If yes, then your scenario is typically a IDOC-to File scenario.
Read this:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
If you do not intend to use XI in between, then you can just configure the outbound IDOCs in your SAP system and configure a file port in we21 transaction and create the partner profile in we20 transaction.
Regards,
Ravi

Help needed on mapping information for AT701 element in EDI X12 214 Transportation type (X12_00401_214 schema)

Hi all,
As per the EDI defined standard schema, AT701 element takes the following Enumeration values.
<xs:element minOccurs="0" name="AT701" type="X12_ID_1650">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo notes="Shipment Status Code_1650" />
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:simpleType name="X12_ID_1650">
<xs:restriction base="xs:string">
<xs:enumeration value="A3" />
<xs:enumeration value="A7" />
<xs:enumeration value="A9" />
<xs:enumeration value="AF" />
<xs:enumeration value="AG" />
<xs:enumeration value="AH" />
<xs:enumeration value="AI" />
<xs:enumeration value="AJ" />
<xs:enumeration value="AM" />
<xs:enumeration value="AN" />
<xs:enumeration value="AP" />
<xs:enumeration value="AR" />
<xs:enumeration value="AV" />
<xs:enumeration value="B6" />
<xs:enumeration value="BA" />
<xs:enumeration value="BC" />
<xs:enumeration value="C1" />
<xs:enumeration value="CA" />
<xs:enumeration value="CD" />
<xs:enumeration value="CL" />
<xs:enumeration value="CP" />
<xs:enumeration value="D1" />
<xs:enumeration value="I1" />
<xs:enumeration value="J1" />
<xs:enumeration value="K1" />
<xs:enumeration value="L1" />
<xs:enumeration value="OA" />
<xs:enumeration value="OO" />
<xs:enumeration value="P1" />
<xs:enumeration value="PR" />
<xs:enumeration value="R1" />
<xs:enumeration value="RL" />
<xs:enumeration value="S1" />
<xs:enumeration value="SD" />
<xs:enumeration value="X1" />
<xs:enumeration value="X2" />
<xs:enumeration value="X3" />
<xs:enumeration value="X4" />
<xs:enumeration value="X5" />
<xs:enumeration value="X6" />
<xs:enumeration value="X8" />
<xs:enumeration value="XB" />
</xs:restriction>
</xs:simpleType>
Now, in my sample input file I am having a column "MileStone", and for example: If I have
"Picked Up Date" in that column, I need to pass "A3" as the value for
AT701 element as per the above code snippets.
Please let me know how to map the "Milestone to "AT701" element.
If I straight away map those two fields, I am getting the below error :
error btm1046: Output validation error: The 'AT701' element is invalid - The value 'MileStone_0' is invalid according to its datatype 'http://schemas.microsoft.com/BizTalk/EDI/X12/2006:X12_ID_1650' - The Enumeration constraint failed.
So, please guide me on how to map the above fields using the functoids.
Thanks in Advance..

Hi Anand,
You can try
Value Mapping functiod along with Logical Equal functiod for this requirement.
Connect the element “MileStone”
to the Logical Equal functiod as the it’s first parameter. And add “Picked Up Date”
as the second parameter.
Connect output of the Logical Equal functiod as the first parameter to the Value Mapping functiod and “A3"
as the second parameter.
Connect the output of
Value Mapping functiod “AT701”
element.
This maps the value “A3”
to the element “AT701”, if the value of “MileStone” element is
“Picked Up Date”
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Seeburger help required for Supplier Invoice (EDI 810) and Dispatch Advice

Hi All,
Pls let me blog/steps for scenario for Supplier Invoice and Dispatch Advice using Seeburger.
For Supplier Invoice I assume R/3 will send data to Vendor (810).
1. Pls let me know for R/3 to XI will we use INVOCE IDOC?
2. Pls let me know for R/3 to XI Communication do we will use same Distributiion Model setup?
3. Pls let me know what Seeburger BIC modules I need to use in Seeburger AS2/File Receiver Adapter
4. Which Interface and Adapter I need to use for 810 and which Interface and Adapter I need to use for 997.
    Pls send its setup with its Mappings defined in Modules.
5. What is Disptach Advice? Is it also same like Supplier Invoice ? Does it also have EDI Number and if yes then what?
Pls send me blogs for the above Supplier Invoice and Dispatch Advice settings.
Regards

>
Rickkk wrote:
> Hi Ravi and All
>
> I am thankful to all of you for great help of yours.
>
> Steps:
>
> 1) I wil create an INvoice in your backend system. It will generate an IDOC.
> 2) This IDOC will be sent to my XI system.
> 3) I will map the IDOC to the Target XML 810 --- From where I will get this Target XML 810 ?
YOu have to login to the Physical box in which XI is installed (Take Basis Help.
In one of the drives, you will find a folder called seeburger.
Inside that folder, you can browse to find the XSD structure for your 810 .
YOu will find different XSDs for different versions of 810.
Suppose your EDI 810 version is 4010, then you have to use the XSD for 810 4010 version (There will be separate folders for each transaction set/version combination.
It will be there also in the software CD that seeburger provides when you buy it.
> 4) I need a seeburger receiver AS2 adapter that consist of modules that will convert the XML 810 docuemnt to EDI document.
>
> Below are the modules will be present in you suggested seeburger receiver AS2 adapter
> module key                  Parameter name               Parameter value
> bic                                destSourceMsg               MainDocument
> bic                                destTargetMsg                MainDocument
> bic                                mappingName                  <the name of your X2E mapping for 810>
> exit                               JNDIName                         deployedAdapters/SeeXIAS2/shareable/SeeXIAS2
>
Yes.
> 5. As per blog -
/people/rajeshkumar.pasupula/blog/2009/08/05/wanna-implement-seeburger-for-edi-find-the-booster
>
> For 997 Interface we are using seeburger Sender adapter and for 850 Interface we are using Split997 Sender adapter -- Reverse order
>
> For this scenario will it be like this again like
> For 997 Interface we will use Seeburger Receiver AS2 Adapter where the above modules are configured -- Pls suggest
>
> For 810 Interface we will use Split997 Receiver adapter -- No modules configured Pls suggest
>
> I request you to kindly send me snapshots or blogs which has snapsot for this scenario.
>
No need of split 997 in outbound case. In this case, you will send the 810 and the partner will send the 997.
So, to receive that 997 file, you need another scenario. You need the split 997 communication channel only in inbound case like in 850, but not in outbound case.
> Last point -- is Dispatch advice direction is like 850 (Inbound ) or its direction is like 810 (outbound)?
> Do we have IDOC or something like that present and its mapping ?
>
like I said earlier, it is an outbound document if your company is the vendor.
It will be inbound if your company is the Customer to some other company.
The IDOC that is used usually will be DESADV idoc.
> Regards

EDI - IDoc - User Exit - Code - Problem - Help - Wanted

Hi EDI Experts,
I have extended ORDERS05 IDOC twice.
ZVKSEG1 is the the segment under extended idoc ZVKORDRS05. This is for one partner.
Z1DATESH01 is the segment under extended idoc Z1ORDER05. This is for another partner.
I have completed the configuration thing in WE82 for both the extensions.
Now the requirement is, whenever a PO is created for the first partner - 100290, the IDoc generated should contain the extra segment ZVKSEG1 and whenever PO is created for the second partner - 10099,the Idoc generated should contain the extrasegment Z1DATESH01.
Using WE20, i have added the extended IDoc type in both the partner profiles under ORDERS message type.
Now i've written the user exit for this using EXIT_SAPLEINM_002.
tables: edidc.
data: z_edidd like edidd occurs 0 with header line.
data: y1dath01 like z1datesh01.
data: yvkseg1 like zvkseg1.
if edidc-rcvprn = '10099'.
z_edidd[] = int_edidd[].
loop at z_edidd.
if z_edidd-segnam = 'E1EDK01'.
read table z_edidd with key segnam = 'Z1DATESH01'.
if sy-subrc <> 0.
y1dath01-DELDATE = sy-datum.
clear z_edidd.
z_Edidd-sdata = y1dath01.
z_Edidd-segnam = 'Z1DATESH01'.
append z_edidd.
endif.
endif.
endloop.
int_edidd[] = z_edidd[].
elseif edidc-rcvprn = '100290'.
z_edidd[] = int_edidd[].
loop at z_edidd.
if z_edidd-segnam = 'E1EDK01'.
read table z_edidd with key segnam = 'ZVKSEG1'.
if sy-subrc <> 0.
yvkseg1-name1 = 'ZVK Chemicals'.
clear z_edidd.
z_Edidd-sdata = yvkseg1.
z_Edidd-segnam = 'ZVKSEG1'.
append z_edidd.
endif.
endif.
endloop.
int_edidd[] = z_edidd[].
endif.
Could you please go through the code and tell me where did i go wrong. The extra segments are not being created for both the partners.
I created PO using ME21n once for each vendor.
Please help me out guys.
Thanks,
Matt

I myself fixed this problem. I made use of XLFA1-LIFNR to manipulate the partner numbers.
Thanks

Need Help in EDI

Hi Dear friends,
I have configured all Automatich payment programme.
please show the steps for EDI
when i am creating this EDI partnar profile.
Maintain the partner profiles for the selected partner number.
just i put the Partner no - CITI
Partnar Type - B
then how to cretae this Agent
in Post Processing : Permitted Agent
type ;
Agent :
in Transaction code WE20
Please help me friends....

hi samsd,
post it in "bmp and workflow"
SAP Business Workflow

Conversion Agent - (EDI - XI - IDOC) - Help

Hi Experts,
I am working on the scenario (EDI - XI - IDOC) using Conversion Agent for Converting EDI data into XML.
I am facing many problems in Real Time, can any one who has already worked on the same scenario send me complete scenario with screen shots,
I need immediate help, really it is very urgent for me.
Regards,
Study SAP

Hi Kishore,
Thanks for your reply, We are using Standard IDOC Orders05 and EDI message ANSI X12 - Message Type 850 for Purchase Order.
Posting EDI Data of Purchase Order in R/3 Sales Order as INBOUND Message.
Using Conversion Agent Parser for the same and deployed this project at Integration Server in ServiceDB Directory.
The Conversion Module CMTransformBean is also deployed at XI Server.
When we are puting file at FTP Server, our XI System is not picking up file while using Conversion Agent Module,
while it is picking up without conversion module successfully.
Please help,
Regards,
Study SAP
[email protected]

Need help with output type EDI for ERS

All,
I want to be able to run and ERS settlement and have the invoices created sent via EDI/XML to the supplier.   I have several questions on the set up.
1) I have output type ERS6 which is defined as ERS EDI. I assume because it does not start with Z* this is SAP standard, so I shouldn't have to modify any of this.
2) I've added my supplier to this output type.
3) I assume I need to create a partner profile for this supplier? If so can someone tell me the message type to use?
Is there any set up I'm missing in this process?   I've executed ERS but do not get an idoc and I'm fairly certain it's because I haven't done the partner profile set-up.
Thanks for your help.
Sandra

Hi,
You don't have to modify thise setup unless you have any customized requirement.
You are missing partner profile setup.Carry out the setup and run MRRL tcode to create the idocs
Enter the following values using tcode WE20.
Field                                       Value
Message type                         GSVERF
Partner type                             LI (vendor)
Partner function                        LF (vendor)
Port                                         SUBSYSTEM ( Port to your middleware)
Output mode                            such as Collect IDocs
Basic type                                GSVERF01
Application                                 MR
Output type                                ERS6 or the type you have defined
Regards,
Karuna

HELP!!! - EDI Outbound HTTP call failure

Our EDI outbound (HTTPS-OXTA) is failing since Monday in production. We narrowed down the area that might be an issue. This is what we see in the Apache log,
[Tue May 22 01:31:56 2012] [debug] opm_ew.c(469): OPM: EW: Enters opm_ew_broadcast()
[Tue May 22 01:31:56 2012] [debug] opm_ew.c(517): OPM: EW: Broadcasts msg: cmd=Broadcast&<serverName>&8001&1337662614&JServ&DiscoGroup&<server_url>&1&1&0&31490&17001;FormsGroup&<server_url>&1&1&0&31491&18001;OACoreGroup&<server_url>&1&1&0&31489&16001;XmlSvcsGrp&<server_url>&1&1&0&31492&19001
[Tue May 22 01:31:56 2012] [debug] opm_hc.c(291): OPM:hc: Connecting to url: <server_url>:8101/oprocmgr-service
[Tue May 22 01:31:56 2012] [debug] opm_hc.c(314): OPM:hc: Connection to host: <server_url>, port: 8101
[Tue May 22 01:31:56 2012] [debug] opm_hc.c(438): OPM:hc: HTTP Request sent to server: POST /oprocmgr-service<server_url> HTTP/1.1^M
Host: <server_url>^M
Content-Type: application/x-www-form-urlencoded^M
Content-Length: 269^M
cmd=Broadcast&<serverName>&8001&1337662614&JServ&DiscoGroup&<server_url>&1&1&0&31490&17001;FormsGroup&<server_url>&1&1&0&31491&18001;OACoreGroup&<server_url>&1&1&0&31489&16001;XmlSvcsGrp&<server_url>&1&1&0&31492&19001
[Tue May 22 01:31:56 2012] [debug] opm_hc.c(808): OPM:hc: headers[0] is HTTP/1.1 404 Not Found
[Tue May 22 01:31:56 2012] [debug] opm_hc.c(808): OPM:hc: headers[1] is Date: Tue, 22 May 2012 05:31:56 GMT
[Tue May 22 01:31:56 2012] [debug] opm_hc.c(808): OPM:hc: headers[2] is Transfer-Encoding: chunked
[Tue May 22 01:31:56 2012] [debug] opm_hc.c(808): OPM:hc: headers[3] is Content-Type: text/html; charset=iso-8859-1
[Tue May 22 01:31:56 2012] [debug] opm_ew.c(525): OPM: EW: Broadcasts to <server_url> and send result=404
I'm trying to understand the steps of the process. Does "HTTP/1.1 404 Not Found" response to the opm_hc.c(438) call? When I type "<server_url>:8101" in the browser, I get "The webpage cannot be displayed" error. Does this should work?
EDI outbound is routed to proxy and confirmed that call from OTA was never made to proxy. Switched protocol to SMTP and it worked. There is no issue other than HTTP initial call failure. Any help you can give me I'd appreciated.

George great support so far (+5)
Hi Robert
debug ccsip all is very intensive so you should do the following before enabling the debug
service sequence-numbers
service timestamps debug datetime localtime msec
logging buffered 10000000 debug
no logging console
no logging monitor
default logging rate-limit
default logging queue-limit
Then..
<Enable debugs, then test again.>
debug ccsip all
<Enable session capture to txt file in terminal program.> (such as Putty)
then do the ff:
terminal length 0
show logging
++++
What is even more strange is that the call appears to be disconnected from the far end. From the logs below the outbound call leg (45) is where the disconnect is coming from and the "cc_api_call_disconnected" shows this call leg talking to CCAPI..
001858: *Jan 20 13:18:19.102: //45/8B56ECEE8011/CCAPI/cc_api_call_disconnected:
Cause Value=16, Interface=0x3CE6D670, Call Id=45
001859: *Jan 20 13:18:19.102: //45/8B56ECEE8011/CCAPI/cc_api_call_disconnected:
Call Entry(Responsed=TRUE, Cause Value=16, Retry Count=0)
Can you also send a debug voip ccapi onout from the CUBE. we need to check if the call arrives there, though we don't see any INVITE request sent out.

PLEASE HELP ME WITH ALE,IDOCS,EDI

Hey SAP Experts
can you guys help me out with <b>ALE,IDOCS,EDI,SOL </b><b>MAN</b> materials please .
mail them to [email protected]
Thanks a lot in Advance
sd learner

Hi,
Please check this online document for ALE and IDoc.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
Also check this links for additional information.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
For Solution Manager, please check links.
http://www.sap.com/services/pdf/BWP_SB_SAP_Solution_Manager.pdf
http://service.sap.com/solutionmanager
Regards,
Ferry Lianto
Please reward points if helpful.

Help creating edi 837 REF*D9 segment

I need to create the REF*D9 segment for our trading partner. Our current edi process does not generate this segment. The segment is basically a copy of the REF*F8 segment, except for the REF01 qualifier being different. I have been able to
generate the segment when the REF*F8 is in the subscriber loop, but the F8 segment can also be created in 2 other loops further down the schema (in the TS837_2330B loop). I have tried numerous solutions for this failing each time. I was told that XSLT would
be best, but am not sure of the logic to use. I am new to BizTalk and XSLT, so I am not even sure of the syntax or how to reference the fields. This process is using 837P schema for source and destination. Could someone please help me out with how to populate
this D9 segment, no matter what loop the F8 segment is created in? Thanks, I appreciate the help.

I have been trying, but I guess I just don't get it. For the most part the mapping is a direct copy of the EDI 837. Main difference being that the trading partner needs the claims split into one claim per ST/SE segment (which I have working fine),
and they require a REF*D9 segment. Our claims system does not generate the REF*D9 segment, but it is a copy of the REF*F8 segment. Problem there is that REF*F8 is generated in one of 3 spots. And two of those are deep in loops. I have tried the Index
functoids. I have gone down to index level 9, still not getting info. I have looked at the code to see what is being selected. I have tried scripting functoids and selecting the element the same way. Doesn't work (don't know what I am doing wrong). I
have tried looping functoids. Seems like no matter what I try I can only generate the REF*D9 when the REF*F8 segment is generated in the 2300 loop, under REF_SubLoop_5 in the REF_PayerClaimControlNumber. If it is generated anywhere else, I
can't seem to pick it up. Again I am very new to BizTalk and XSLT, any other ideas for me to try? Thanks.

Edi-help

Similar Messages

Maybe you are looking for