Edi 855 and 850

hi all , Does anyone have mapping instructions/template to map IDOC (ORDRSP message) to EDI X12 Purchase Order Acknowledgment (855)?
I'd greatly appreciate any help.

Hi,
Check this links for Content Master.
http://help.sap.com/saphelp_nw04/helpdata/en/43/6d95e0ac846fcbe10000000a1553f6/CMGetStart.pdf
http://help.sap.com/saphelp_nw04/helpdata/en/43/4c38c4cf105f85e10000000a1553f6/content.htm
IF u need any docs on content master,give ur mail id i will provide.
Regards,
Phani
Reward points if Helpful

Similar Messages

  • 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 855 messgae mapping to ORDRSP

    Hi,
    I would like to map Vendor confirmation number  coming from EDI 855 to the ORDRSP idoc.
    Please suggest which segment with qualifier and fields in it can be used for this purpose to log the confirmation number in SAP.
    Thanks,
    Venu.

    Hi Savitha,
    Thanks for the reply.
    I have tried this option at header level (E1EDK02-002) and item level (E1EDP02-002)too previously, but it is not working.
    I'm currently working in SAP 4,7 version, do I need to implement any notes to accept the vendor number and update externaldoc number?
    In the standard SAP code before updating vendor number... item details are checking against PO, If I give PO number it is updating the same at External doc number.
    Thanks,
    Venu.

  • EDI 855 (Order Confirmation)

    One of our customers is requiring us to send them an EDI 855 whenver we change a sales order.  They only want the 855 if something is changed.  I thought about using output type BA00 with message type ORDRSP, however the idoc doesn't tell you what has changed and this is required by the cusotmer on the 855.  For example, if we change the qty from 10 to 8, this needs to be on the IDOC in order for it to be mapped on the 855.  Has anyone dealt with this type of 855 before?  Thank you,

    MxG,
    For both plant and pricing condition functional config was already done. If any of these two fields are missing, the status of sales order will be incomplete.For incomplete orders also, the EDI output is being proposed.
    Now just tell me, in which SAP program, do i have to put the break point?
    Where exactly ??
    Thanks and kind regards,
    Creasy Matt

  • Passing EDI filename for 850 from B2B Gateway to BPEL

    Hi,
    Is there any way to pass the EDI filename for 850 from B2B Gateway to BPEL via AQ? we want to store the inbound filename in the database along with the PO.
    we are using 10g.
    Thanks,
    Naveen

    Hi Naveen,
    Generally this could be done using the message id only as mentioned by ew. Just what you need to do is to lookup in the table and find the payload corresponding to that message id.
    However, WORKAROUND would be to use "Preserve Filename" feature of 11g B2B (which works only for FILE,FTP and SFTP transport protocols). In this case you have to pass the filename in the header "ACTION", as mentioned by Nitesh.
    Regards,
    Anuj

  • Send an automatic acknowledge EDI 855

    Hi there,  I’m working in an Idoc integration and EDI using Inovis as middleware, actually I’m receiving ORDERS05 Idoc from Inovis to create a Sales Order, I need to trigger an action at the moment when Sales Order is created in SAP, to send an automatic acknowledge that would be mapped to EDI 855. I would like to know how I can trigger this action in SAP.
    Thanks in advance.

    Hi Alexis,
    to get this configuration working set up
    ORDRSP message
    with message control (we20) entry V1 BA00 SD10
    for such IDOC scensario with screenshot examples check out my book:
    <a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
    you can also check this doc for sales order output (BA00):
    http://help.sap.com/bp_retailv1470/documentation/EN/Merchandise%20Distribution_EN_CUST_V147.doc
    is that what you're looing for?
    Regards,
    michal

  • ANSI X12 xsd of edi 110 and edi 214 document

    Hello All,
    Pl can anyone of you tell me from where to get XSDs of
    edi 110 and edi 214 document (ANSI X12).
    thanks, in advance
    Sharada

    HI,
    Usually when u buy a Seeburger license you need to import the Seeburger software component version in IR and once you immport that you will get the Std seeburger XSD in external definition.
    Thnx
    Chirag

  • EDI, ALE and IDOC

    Hi All,
         I am a Junior ABAP developer. I am new to EDI, ALE and IDOC's. Could someone help me out how to start with this and the necessary material required to go through!!
    Thanks in advance!!

    HI Penchanta ,
    Go through  this links for additional information.
    1.http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    2.http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    3.http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    4.http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    5.http://www.sapgenie.com/sapedi/index.htm
    Regards.
    Note: Reward if useful
    Also check this link from SDN
    (1) /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
    (2) /people/kevin.wilson2/blog/2006/11/13/ale-scenario-development-guide
    (3)http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    (4) idoc
    (5)http://help.sap.com/saphelp_erp2005vp/helpdata/en/78/2178a651ce11d189570000e829fbbd/frameset.htm--
    --This is for Message Control. See the Left Pane in this web page to get the ALE implementation for BAPI's also.
    (6)/people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment - Converson Rules Guidelines

  • EDI 821 and EDI 823 field mapping file and basic IDOC type and message type

    Hi All,
    We are facing some issues regarding EDI 821 and EDI 823 file mappings.
    We are mapping EDI 821 and EDI 823 transactions into SAP using IDOCs. Currently we are using the below entries
    EDI 823 - Lock Box
    Basic IDOC type - FINSTA01
    Message type - FINSTA
    Process Code  - FINS
    The problem is we are able to get the IDOC into SAP with status red and the various errors were due to not able to create the lockbox entry in SAP and once we got yellow status also but the lock box entry was not created and the errors are like No Conversions,no header etc.
    EDI 821 -
    Basic IDOC type - PEXR2002
    Message type - PAYEXT OR REMADV
    Process Code  - PEXC OR REMA
    We are facing the same problem here also and the internal payment order is not creating in SAP and IDOC was generated with yellow status and red status.
    We are trying different combinations but nothing is working so far.
    I need the following things to proceed furthur.
    1)Are the IDOC , Message and process codes are correct that I am using now for both EDI 821 and EDI 823
    2)If those are not correct, can you please let me know the correct entries
    3) Please provide me the field mapping if any one of you have worked earlier for both the above IDOC and message type or new ones and we have one field mapping now but if you can send it to me then  I can re check it.
    4) Do we have to create any configuraion or customizing in SAP to create the IDOC in green status and if so please let me know the customizing steps and procedures for both EDI 821 and EDI 823.
    thanks in advance for all your help.
    Please let me know if my question is not clear.
    Thanks,
    Ramesh.

    Hi Ramesh,
    I believe you are using those interfaces with the business partner type as Bank, Whatever idoc type, message type and process code you have used are perfectly correct.
    First of all did you enable your bank for EDI, the house bank has to be EDI enabled first then only your idoc's can be processed, talk to your fi functional consultant and he might help you.
    Are you can give me the exact error and i can help you as well.
    Thanks,
    Mahesh.

  • What T-Codes do Inbound 855 and Inbound 856 EDITransactions trigger?

    Hi Folks,
    I know inbound 856 is a call transaction method. It triggers VA01 transaction.
    Likewise, Are inbound 855, 856 call transaction methods or not?
    If yes, what transactions (T-Codes) do they trigger?
    What are the process codes  (inbound) for 855 and 856 inbound?
    Thanks,
    Creasy

    Hi
    for sending data from SAP to POS u can use WPMA tcode with the help of that Tcode you can send
    Merchandise category information
    Article master data
    Control data
    EAN
    Bonus buys & coupons
    Promotion discounts
    Assortment lists
    for inbound scenaro -
    you can use standrad IDOC
    like
    WPUBON01 - Sales transactions, receipt-based
    WPUUMS01 - Sales transactions, aggregated
    WPUTAB01 - Means of payment (Upload day-end closing POS)
    WPUKSR01 - Cashier statistics
    WPUFIB01 - Financial transactions
    WPUWBW01 - Goods movements
    and process these IDOC with thep of Tcode BD20 or report RBDAPP01
    PS: Reward Point
    Thanks
    Amit Shivhare

  • Parsing an EDI file and populating the data into database table

    Hi ,
    Please help me in parsing an edi file and getting the required columns.
    we get an EDI file from a bank. I need to parse that file and populate the db table with the required columns.
    the file is '*' delimited and every line ends with '\'.
    The record starts with 'ST*' and ends with 'SE*'.
    sample edi file is
    ISA*00*          *00*          *ZZ*043000096820   *ZZ*2156833510     *131202*0710*U*00401*000001204*0*P*>\  ignore first 2 lines                                                                                                                                                                                              
    GS*RA*043000096820*2156833510*131202*0710*1204*X*003020\                                                                                                                                                                                                                                                  
    ST*820*000041031\                                                                                                                                                                                                                                                                                     
    BPR*X*270*C*ACH*PPD*01*101036669***9101036669**01*031000053*DA*00000008606086714*131202\                                                                                                                                                                                                                  
    TRN*1*101036661273032\                                                                                                                                                                                                                                                                                    
    DTM*007*131202\                                                                                                                                                                                                                                                                                           
    N1*1U*BPS\                                                                                                                                                                                                                                                                             
    N1*BE*MICHAEL    DRAYTON*34*159783633\                                                                                                                                                                                                                                                                    
    N1*PE*BPS*ZZ*183383689C2 ABC\                                                                                                                                                                                                                                                          
    N1*PR*ABC  TREAS 310\                                                                                                                                                                                                                                                                                     
    SE*9*000041031\ ST*820*000041032\                                                                                                                                                                                                                                                                                         
    BPR*X*686*C*ACH*PPD*01*101036669***9101036669**01*031000053*DA*00000008606086714*131202\                                                                                                                                                                                                                  
    TRN*1*101036661273034\                                                                                                                                                                                                                                                                                    
    DTM*007*131202\                                                                                                                                                                                                                                                                                           
    N1*1U*BPS\                                                                                                                                                                                                                                                                             
    N1*BE*SAMIA      GRAVES*34*892909238\                                                                                                                                                                                                                                                                     
    N1*PE*BPS*ZZ*184545710C5 ABC\                                                                                                                                                                                                                                                          
    N1*PR*ABC  TREAS 310\                                                                                                                                                                                                                                                                                     
    SE*9*000041032\
    Below is the procedure I am trying to use for parsing that file. but the logic is not working. can you please help me in doing this. its very urgent requirement.
    CREATE OR REPLACE package body p1 is
    Function parse_spec(p_str varchar2) return t_str_nt is
    begin
          return regexp_replace(p_str,'\\$',null);
    end;
    procedure edi( is
    l_out_file              utl_file.file_type;
    l_lin                 varchar2(200);
    field1            number(9);
    field2                varchar2(10 byte);
    field3           varchar2(15 byte);
    field4               varchar2(15 byte);
    field5              varchar2(20 byte);
    field6             varchar2(20 byte);
    field7              varchar2(20 byte);
    field8                  varchar2(9 byte);
    field9              varchar2(15 byte);
    field10             varchar2(5 byte);
    l_item_nt             t_str_nt:=t_str_nt();
    begin
       l_out_file  := utl_file.fopen (file_path, file_name, 'r');
       IF utl_file.is_open(l_out_file) THEN
        LOOP
          BEGIN
           l_item_nt:= utl_file.get_line(l_out_file, l_lin);
            IF l_item_nt IS NULL THEN
              raise no_data_found;
            Else
              for k in 1..l_item_nt.count loop
                  case
                   when l_item_nt(k) like 'ST*%' then
                           field1:= ltrim(regexp_substr(parse_spec(l_item_nt(k)),'[^*]+',1,3),0);
                   when l_item_nt(k) like 'BPR*X*%' then
                           field2 := regexp_substr(parse_spec(l_item_nt(k)),'[^*]+',1,3);
                    when l_item_nt(k) like 'TRN*1*%' then
                             field3:= regexp_substr(parse_spec(l_item_nt(k)),'[^*]+',1,3);
                    when l_item_nt(k) like 'DTM*007*%' then
                            field4:= regexp_substr(parse_spec(l_item_nt(k)),'[^*]+',1,3);
                    when l_item_nt(k) like '%*BE*%' then
                            field5 := regexp_substr(regexp_substr(parse_spec(l_item_nt(k)),'[^*]+',1,3),'[^ ]+', 1, 1);
                            field6 := regexp_substr(regexp_substr(parse_spec(l_item_nt(k)),'[^*]+',1,3),'[^ ]+', 1, 1);
                             field7  := regexp_substr(parse_spec(l_item_nt(k)),'[^*]+',1,5);
                    when l_item_nt(k) like '%*PE*%*ZZ*%' then
                            field8:= regexp_substr(regexp_substr(parse_spec(line),'[^*]+',1,5),'[^ ]+',1,1)
                            field9 := regexp_substr(regexp_substr(parse_spec(line),'[^*]+',1,5),'[^ ]+',1,2);
                     when l_item_nt(k) like 'SE*%' then
                                                         insert into t1(field1,field2,field3,field5,field6,field7,field8,field9)
                                --  values(field1,field2,field3,field5,field6,field7,field8,field9);
                     else
                            dbms_output.put_line ('end of line');
                         end case;
                end loop;
            end if;
    end loop;
                         utl_file.fclose(l_out_file);
    exception
       when no_data_found then
                   dbms_output.put_line('No data found');
       end;

    I would not use regular expressions for parsing as it is CPU intensive - and standard string processing suffices.
    I would break the EDI up into lines. I would tokenise each line. I then have 2d array that can be referenced to find a specific field. E.g. line x and token y is field abc.
    Basic approach:
    SQL> create or replace type TStrings as table of varchar2(4000);
      2  /
    Type created.
    SQL> -- create a parser that tokenises a string
    SQL> create or replace function Tokenise(
      2          csvLine varchar2,
      3          separator varchar2 default ',',
      4          enclosedBy varchar2 default null
      5  ) return TStrings is
      6          strList         TStrings;
      7          str             varchar2(32767);
      8          i               integer;
      9          l               integer;
    10          enclose1        integer;
    11          enclose2        integer;
    12          encloseStr      varchar2(4000);
    13          replaceStr      varchar2(4000);
    14
    15          procedure AddString( line varchar2 ) is
    16          begin
    17                  strList.Extend(1);
    18                  strList( strList.Count ) := Replace( line, CHR(0), separator );
    19          end;
    20
    21  begin
    22          strList := new TStrings();
    23
    24          str := csvLine;
    25          loop
    26                  if enclosedBy is not null then
    27                          -- find the ennclosed text, if any
    28                          enclose1 := InStr( str, enclosedBy, 1 );
    29                          enclose2 := InStr( str, enclosedBy, 2 );
    30
    31                          if (enclose1 > 0) and (enclose2 > 0) and (enclose2 > enclose1) then
    32                                  -- extract the enclosed string
    33                                  encloseStr := SubStr( str, enclose1, enclose2-enclose1+1 );
    34                                  -- replace the separator char's with zero char's
    35                                  replaceStr := Replace( encloseStr, separator, CHR(0) );
    36                                  -- and remove the enclosed quotes
    37                                  replaceStr := Replace( replaceStr, enclosedBy );
    38                                  -- change the enclosed string in the big string to the replacement string
    39                                  str := Replace( str, encloseStr, replaceStr );
    40                          end if;
    41                  end if;
    42
    43                  l := Length( str );
    44                  i := InStr( str, separator );
    45
    46                  if i = 0 then
    47                          AddString( str );
    48                  else
    49                          AddString( SubStr( str, 1, i-1 ) );
    50                          str := SubStr( str, i+1 );
    51                  end if;
    52
    53                  -- if the separator was on the last char of the line, there is
    54                  -- a trailing null column which we need to add manually
    55                  if i = l then
    56                          AddString( null );
    57                  end if;
    58
    59                  exit when str is NULL;
    60                  exit when i = 0;
    61          end loop;
    62
    63          return( strList );
    64  end;
    65  /
    Function created.
    SQL>
    SQL>
    SQL> declare
      2          ediDoc  varchar2(32767) :=
      3  'ISA*00*          *00*          *ZZ*043000096820   *ZZ*2156833510     *131202*0710*U*00401*000001204*0*P*>\GS*RA*043000096820*2156833510*131202*0710*1204*X*003020\ST*820*000041031\BPR*X*270*C*ACH*PPD*01*101036669***9101036669**01*031000053*DA*00000008606086714*131202\TRN*1*101036661273032\DTM*007*131202\N1*1U*BPS\N1*BE*MICHAEL      DRAYTON*34*159783633\N1*PE*BPS*ZZ*183383689C2 ABC\N1*PR*ABC  TREAS 310\SE*9*000041031\ST*820*000041032\BPR*X*686*C*ACH*PPD*01*101036669***9101036669**01*031000053*DA*00000008606086714*131202\TRN*1*101036661273034\DTM*007*131202\N1*1U*BPS\N1*BE*SAMIA        GRAVES*34*892909238\N1*PE*BPS*ZZ*184545710C5 ABC\N1*PR*ABC  TREAS 310\SE*9*000041032\';
      4
      5          lines   TStrings;
      6          tokens  TStrings;
      7  begin
      8          -- split EDI string into lines
      9          lines := Tokenise( ediDoc, '\' );
    10
    11          -- process line and extract fields
    12          for i in 3..lines.Count loop
    13                  dbms_output.put_line( '***********************' ) ;
    14                  dbms_output.put_line( 'line=['||lines(i)||']' );
    15                  tokens := Tokenise( lines(i), '*' );
    16
    17                  for j in 1..tokens.Count loop
    18                          dbms_output.put_line( to_char(j,'00')||'='||tokens(j) );
    19                  end loop;
    20          end loop;
    21  end;
    22  /
    line=[ST*820*000041031]
    01=ST
    02=820
    03=000041031
    line=[BPR*X*270*C*ACH*PPD*01*101036669***9101036669**01*031000053*DA*00000008606086714*131202]
    01=BPR
    02=X
    03=270
    04=C
    05=ACH
    06=PPD
    07=01
    08=101036669
    09=
    10=
    11=9101036669
    12=
    13=01
    14=031000053
    15=DA
    16=00000008606086714
    17=131202
    line=[TRN*1*101036661273032]
    01=TRN
    02=1
    03=101036661273032
    <snipped>

  • EDI 850 and EDI 855 differences

    Hi All,
    We are currently receiving a PO Via EDI-850 and Sales document is posted. Due to the internal setting based on several scenario's either the material or qty gets changed eg Material determination. Price also what they send on the EDI and current condition record rate may be different.  Sales orders are created based on the condition record.  Upon saving the order it sends the Order Acknowledgement ie 855. 
    Any standard  SAP functionality is available to mark the differences on the PO received via EDI 850, before sending the 855 back to the customers.
      Your feedback is apperciated.
    Thanks,

    Hi Shobha,
    Maybe you could create requirement routine for the output type of Order Acknowledgement to check whether the PO data consist with SO data and stop the output process if the data doesn[t consist.
    Then you could enter another output type without the requirement check manually on the sales order after getting acknowledge of the differences.
    Hope it helps.
    Best regards,
    Smile

  • EDI 855 FIRST_ACK_CODE EXPLANATION REQUIRED

    HI All,
    Does anyone know the secrets to the mystery of the OE_HEADER_ACKS and OE_LINE_ACKS tables in EBS R12Order Mgmt.? Allow me to explain.
    We are implementing EDI to receive inbound orders from our customer. Customer sends an inbound 850 purchase order; we receive via the Oracle e-Commerce Gateway and load into OM as sales orders via the sales order interface.
    For such uploaded SOs, we need to send back an order acknowledgement to the customer via an outbound 855 EDI transmission. Using the seeded EBS 11i functionality, we are able to get the system to populate the acknowledgement tables, OE_HEADER_ACKS and OE_LINE_ACKS, when such EDI orders have been booked.
    But these tables have columns with various codes. For example, the OE_HEADER_ACKS.FIRST_ACK_CODE column may have a value of AC or AT, but what do these seeded codes mean?
    OE_HEADER_ACKS.FIRST_ACK_CODE have values IA,SP,IB,DR,IQ
    I cannot find 1 Metalink doc that explains the purpose or meaning of these codes. I can't find any OAUG white papers that explain either.
    Any help would be appreciated!

    thanks hussein for ur reply,
    I have already seen the above url , but there is no description for the FIRST_ACK_CODE coulmn value such as SP,DR,ID,IQ,IC,IP,IB etc
    Please help me in thIS
    Thanks

  • Vocabulary not getting executed for EDI 855 data

    Hello,
    I am trying to pull data from EDI file using vocabulary. But it's not returning any value. 
    xpath selector - 
    /*[local-name()='X12_00401_855' and namespace-uri()='http://schemas.microsoft.com/BizTalk/EDI/X12/2006']/*[local-name()='N1Loop1' and namespace-uri()='http://schemas.microsoft.com/BizTalk/EDI/X12/2006']/*[local-name()='N1' and namespace-uri()='http://schemas.microsoft.com/BizTalk/EDI/X12/2006'][*[local-name()='N101'
    and namespace-uri()='']/text()='ST']
    xpath field -
    *[local-name()='N104' and namespace-uri()='']/text()
    Can anybody help me on this ? 

    No error message. But after I realized that I am not executing instruction loader policy before the rule that uses the vocabulary, then I created instruction loader policy to set the document type for 855 schema.
    But that policy is throwing an exception now. "An exception occurred while executing the policy"

  • Sender / Receiver ID mapping for EDI interfaces and Type of seeburger adapt

    We need to set up a interface using Seeburger adapter for Purchase order IDOC to 850 EDI mapping.. After reading from SDN,
    1) We can use the standard mapping in BIC MD to do E2X and X2E mapping..
    2) We can use any of the AS2, EDI generic adapter, Seeburger FTP adapter or Seeburger SFTP adapter...
    How do we decide which adapters should be chosen? I can see that it makes sense to use SFTP adapter or AS2 adapter for security...
    Also how do we map Sender and Receiver IDs on the EDI message.. Should this be hardcoded as part of mapping or is there any facility in seeburger adapter to do this? I saw some references to Party Identifiers and not sure how it is used in setting up Sender/ Receiver ID
    Also the graphical mapping to convert IDOC XML to EDI XML, Do we have standard mapping defined or do we need to create our own graphical mapping.

    Hi Kris,
    I had worked in the somehow same scenario, It was IDOC to EDIFACT file.
    I can give you few clues which might be helpful
    In BIC MD you have to create your own mapping if the standard mapping is not available (First check all the standard mappings in BIC). For your reference you need X2E mapping, as your scenario is IDOC to 850 EDI.
    "the graphical mapping to convert IDOC XML to EDI XML, Do we have standard mapping defined or do we need to create our own graphical mapping."
    In graphical mapping i created my own mapping, Seeburger has given some sample mappings you can check those for your reference (SEEBURGER_GENERIC_EDI software component). Mostly you have to create your own. You need a document from your functional consultant so that you are able to map correct fields and constants.
    "how do we map Sender and Receiver IDs on the EDI message.. Should this be hardcoded as part of mapping or is there any facility in seeburger adapter to do this? I saw some references to Party Identifiers and not sure how it is used in setting up Sender/ Receiver ID"
    This has been generally hardcoded in message mapping (In my case i hardcoded). If any of ur IDOC field contains that data you can map that field. But better Idea is ask your functional expert.
    "How do we decide which adapters should be chosen? I can see that it makes sense to use SFTP adapter or AS2 adapter for security... "
    You can choose adapter according to your requirement. In my case i used File adapter as i have to create file in PI server only. My suggestion you can use SFTP for seeburger
    Hope these points are helpfu for u
    Regards,
    Shradha

Maybe you are looking for