EDI Inbound-Port definition

Hi,
We are doing EDI Inbound for PO. For this I need to define the port(Sender Port) as in the control record(i.e as they r sending) .If they change their port it is not working what shold I do for this.
regds,
Vinsa.R

Hi,
As i mentioned before, the sender should inform any change in control parameter so you can change your port too.
Check with the sender if they can provide this information before changing. I do not what is the terms of your company with this sender, but they should inform you before doing any change.
<b>Option-2</b>
The other option you have is, you create your custom program which runs before RSEINB00. In this program you have to,
- read each and every file from this UNIX directory
- read the control record.
- check if SNDPOR is what you have defined in your system
- if not then change it and save it back.
You can check the source code of FM <b>'IDOC_INBOUND_FROM_FILE'</b> to see how SAP read this file. ( Program RSEINB00 calls this FM internally ). This will give you an idea, how to read control record.
I do not know if option-2 of changing control record in file will affect anything else or not.
Let me know if you have any question.
Regards,
RS

Similar Messages

EDI: Receiver port in control record is invalid

Yesterday, we got refreshed out quality system with the production SAP system.
I am trying to process IDoc # QXXXXXXX in quality but I am getting the following error message:
EDI: Receiver port in control record is invalid.
To create this IDoc, I copied IDoc # PXXXXXXX using WE19 and modified certain fields so that it would change the clearance status. The IDoc I used to copy from was from production server and a part of the recent refresh of Production serveru2026
could that be the reason that the EDI Receiver port is invalid or is there another reason?
THANKS IN ADVANCE.

Hi sam kumar
Ports and Partner Profile may be Same or Different in Quality and Production systems.- it is Client dependent
U can cross check Ports using WE21 with Quality system and production systems
U can cross check Partner Profile using WE20 with Quality system and production systems
if both are not same u need maintain port and partner profiel before creating idoc using we19...
Note: Keep a note on Logical system also..
I hope this help for all when system refreshs,.
Ramesh

EDI: Sender port in control record is invalid

HI
EDI: Sender port in control record is invalid, this message i am getting in WE02 what is this pls tell me ASAP
regards
shekar

Hi,
Check the ALE setting...
STEP 1:ALE SETTINGS TO POST IDOC OUT OF SAP R/3
We need to do the following settings in XI
1) Create an RFC Destination to the Sending System in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client
d) Enter the RFC Destination created in SAP R/3 towards other system
e) Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) Create an RFC Destination to XI in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client user & Password details of Destination system
h) Test the connection and remote logon.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Outbound Parameters (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Outbound Parameters.So click on ADD TO Create Outbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Receiving port, Pack size=1 and Basic type
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
5) Create Customer Distribution model in the transaction code BD64
1) Click on the Create modal View button and enter the short text, Technical name etc as shown below
2) Now select the created model view and click on Add message type button .A pop up box appears, enter Sending system, receiving system and message type
3) Save the Distribution model
Generate Partner Profiles
Click on Menu Item Generate Partner Profiles
It leads to the next transaction where in the selection screen you have to provide Model view name, Partner System logical system and execute
Then, you will be intimated about the partners, port creation, and outbound parameters creation
4) Distribute Customer Distribution Model
In the menu item GO to Edit->Modal View-> Distribute to the destination client
Popup window appears ,press Enter
You will be intimated about the the Modal View Distributed
Regards,
Phani

Oracle EDI Inbound & Outbound setup docs R12.1.3 overview

Hi Gurus,
Please share with me setup docs for Oracle EDI Inbound & Outbound . If possible Pros and Cons of EDI .. as we're suggesting this for one of our esteemed client in UK.
Also let me know below are possible are not with Oracle EDI functionality :
Plug in custom solution or logic to dervice item Pricing, Item Cross Reference and Unit of Measure while creating Sales order in EBS ?
Many thanks,
Mahe

Duplicate - Oracle EDI Inbound and Outbound setup docs R12.1.3

EDI : inbound processing error.

Hi All,
I am facing the below error
"Entry in inbound table not found" status 56.
I am setting a new EDI inbound interface for goods reciept GR:
We have got a flat file which we are trying to upload from SAP directory.
after uploading i am getting the above error. The error points at Partner Profile details stating the details doesnot exist. But i cross checked and its all correct.
- Partner Profile created.
- Message type exixt in INBOUND Parameters.
If i reprocess this failed idoc using we19 selecting INbound function module "L_IDOC_INPUT_WMMBXY" then it gets processed successfully.
If i reprocess this failed idoc via editing and then running report RBDINPUT for processing edited idoc status 69, then the probelm persist.
I dont know what i am missing.
Thanks in advance.

Hi,
I am getting the same error.
Can u please help me on this.
Thanks and Regards
Neha Kapoor

EDI inbound Purch Order - Changes needed

Hi all,
I have EDI inbound purchase orders that get created into sales orders in sap. This use message type ORDERS and process code ORDE.   Question is for some of these inbound purchase orders, i may need to add a new material to existing sales orders that are created previously. To make changes to existing sales order, can i use the same message type and process code ?     Have anyone come across such situation ?
thanks
Joyce

Hi Joyce,
The IDOC Type remains the same for create/change/confirmation etc, the system uses the partner profile to know the kind of action it must take on a given IDOC, parameters like message type and process code help the system to process the IDOC accordingly.
IDOC Type      Message Type      Process Code      Action taken
ORDERS05     ORDERS                 ORDE                  Create Order
ORDERS05     ORDCHG                ORDC                  Change Order
ORDERS05     ORDRSP                 ORDR                  Confirmation
My bad, the segment name is E1EDP01 --- Go to WE30, open up idoctype ORDERS05, look for E1EDP01 segment, double click on this segment and you will see the field ACTION.
Regards,
Chen

EDI Inbound ( need code sample )

Hi Guus,
      I have an object to develop , its and EDI inbound interface . Can some one send me sample code or atleast guide me from where I can start.
Regards
Avi.......

Hi ,
plz go through the below code..
FUNCTION zsd_idoc_input_order_change.
""Local Interface:
*" IMPORTING
*"     VALUE(INPUT_METHOD) LIKE BDWFAP_PAR-INPUTMETHD
*"     VALUE(MASS_PROCESSING) LIKE BDWFAP_PAR-MASS_PROC
*" EXPORTING
*"     REFERENCE(WORKFLOW_RESULT) LIKE BDWFAP_PAR-RESULT
*"     REFERENCE(APPLICATION_VARIABLE) LIKE BDWFAP_PAR-APPL_VAR
*"     REFERENCE(IN_UPDATE_TASK) LIKE BDWFAP_PAR-UPDATETASK
*"     REFERENCE(CALL_TRANSACTION_DONE) LIKE BDWFAP_PAR-CALLTRANS
*" TABLES
*"      IDOC_CONTRL STRUCTURE EDIDC
*"      IDOC_DATA STRUCTURE EDIDD
*"      IDOC_STATUS STRUCTURE BDIDOCSTAT
*"      RETURN_VARIABLES STRUCTURE BDWFRETVAR
*"      SERIALIZATION_INFO STRUCTURE BDI_SER
*" EXCEPTIONS
*"      WRONG_FUNCTION_CALLED
Work areas for the idoc tables.
DATA: wa_data    TYPE edidd.
status = '53'. "initial
Read the control data information of idoc.
READ TABLE idoc_contrl INTO gwa_control WITH KEY mestyp = 'ZORDRPLY'.
IF sy-subrc EQ 0.
Extract the data from the segments.
    LOOP AT idoc_data INTO wa_data             "LOOP AT idoc_data
    WHERE docnum = idoc_contrl-docnum.
      CASE wa_data-segnam.                     " CASE gwa_data-segnam
        WHEN 'Z1SCSK'.                          "Header data
          MOVE wa_data-sdata TO gwa_z1scsk.
          CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
            EXPORTING
              input = gwa_z1scsk
            IMPORTING
              output = gv_vbeln.
        WHEN 'Z1SCSP'.                          "Item data
          MOVE wa_data-sdata TO gwa_z1scsp.
          CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
            EXPORTING
              input = gwa_z1scsp-posnr
            IMPORTING
              output = gv_posnr.
          gwa_z1scsp-posnr = gv_posnr.
          APPEND gwa_z1scsp TO i_z1scsp.
      ENDCASE.                                 " CASE gwa_data-segnam
    ENDLOOP.                                     "LOOP AT idoc_data
Update the sales order
    PERFORM order_change.
ELSE.
Begin of Mod-001
    status = '51'.
    bapi_retn_info-type       = 'E'.
    bapi_retn_info-id         = 'ZSDM'.
    bapi_retn_info-number     = '028'.
    bapi_retn_info-message_v1 = 'Wrong'.
    bapi_retn_info-message_v2 = 'Message'.
    bapi_retn_info-message_v3 = 'Type'.
   RAISE wrong_function_called.
ENDIF.                                            " IF sy-subrc EQ 0
*Start wf
PERFORM wf_start
             USING
                    idoc_contrl-docnum
                    gv_vbeln
                   CHANGING
                     bapi_retn_info.
*end of starting of wf
*set status
IF status = '53'.
    bapi_retn_info-type       = 'S'.
    bapi_retn_info-id         = 'ZSDM'.
    bapi_retn_info-number     = '028'.
    bapi_retn_info-message_v1 = gv_vbeln.
    bapi_retn_info-message_v2 = 'Changed.'.
    bapi_retn_info-message_v3 = 'Succcessfully'.
ENDIF.
PERFORM idoc_status_ord_change
          TABLES idoc_data
                 idoc_status
                 return_variables
           USING idoc_contrl
                 bapi_retn_info
                 status
                 workflow_result.
End of Mod-001
ENDFUNCTION.
FORM idoc_status_ord_change
     TABLES idoc_data    STRUCTURE edidd
            idoc_status STRUCTURE bdidocstat
            r_variables STRUCTURE bdwfretvar
      USING idoc_contrl LIKE edidc
            value(retn_info) LIKE   bapiret2
            status       LIKE bdidocstat-status
            wf_result    LIKE bdwf_param-result.
CLEAR idoc_status.
idoc_status-docnum   = idoc_contrl-docnum.
idoc_status-msgty    = retn_info-type.
idoc_status-msgid    = retn_info-id.
idoc_status-msgno    = retn_info-number.
idoc_status-appl_log = retn_info-log_no.
idoc_status-msgv1    = retn_info-message_v1.
idoc_status-msgv2    = retn_info-message_v2.
idoc_status-msgv3    = retn_info-message_v3.
idoc_status-msgv4    = retn_info-message_v4.
idoc_status-repid    = sy-repid.
idoc_status-status   = status.
APPEND idoc_status.
IF idoc_status-status = '51'.
    wf_result = '99999'.
    r_variables-wf_param   = 'Error_IDOCs'.
    r_variables-doc_number = idoc_contrl-docnum.
    READ TABLE r_variables FROM r_variables.
    IF sy-subrc <> 0.
      APPEND r_variables.
    ENDIF.
ELSEIF idoc_status-status = '53'.
    CLEAR wf_result.
    r_variables-wf_param = 'Processed_IDOCs'.
    r_variables-doc_number = idoc_contrl-docnum.
    READ TABLE r_variables FROM r_variables.
    IF sy-subrc <> 0.
      APPEND r_variables.
    ENDIF.
ENDIF.
ENDFORM.                    "idoc_status_ord_change
***INCLUDE LZSD_FS007_ORDERCHANGEF01 .
*&      Form order_change
      This Form is used for updating the DB tables(vbap,vbep)        *
FORM order_change .
Declaration of internal tables.
DATA : i_vbap TYPE STANDARD TABLE OF vbap,
         i_vbep TYPE STANDARD TABLE OF vbep.
Declaration of workareas.
DATA : wa_vbap TYPE vbap,
         wa_vbep TYPE vbep.
Declaration of constants.
CONSTANTS : lc_sno(3)     TYPE c VALUE '039',
              lc_ino(3)     TYPE c VALUE '040',
              lc_msg(4)     TYPE c VALUE 'ZSD',
              lc_emsgty(1) TYPE c VALUE 'E',
              lc_smsgty(1) TYPE c VALUE 'S',
              lc_estatus(2) TYPE c VALUE '51',
              lc_sstatus(2) TYPE c VALUE '53'.
Declaration of variable.
DATA : lv_index TYPE syindex,
         lv_zzproddt TYPE sydatum.
Fetch the data from vbap
SELECT * FROM vbap INTO TABLE i_vbap
WHERE vbeln EQ gv_vbeln.
IF NOT i_vbap IS INITIAL.
Fetch the data from vbep
    SELECT * FROM vbep INTO TABLE i_vbep
      FOR ALL ENTRIES IN i_vbap
      WHERE vbeln EQ i_vbap-vbeln
      AND posnr EQ i_vbap-posnr.
Modify production option date (zzproopdt) of i_vbap
and production date(zzproddt) & original production date(zzoprodt)
of i_vbep with the data sent by SCS.
    lv_index = 1.
    LOOP AT i_z1scsp INTO gwa_z1scsp.
      LOOP AT i_vbap INTO wa_vbap WHERE posnr = gwa_z1scsp-posnr.
        IF sy-subrc EQ 0 .
Copies the date value in gwa_z1scsp-zzproopdt to wa_vbap-zzproopdt,
if valid date is there in gwa_z1scsp-zzproopdt
          PERFORM validate_date USING gwa_z1scsp-zzproopdt
                                      wa_vbap-zzproopdt.
          IF NOT wa_vbap-zzproopdt IS INITIAL.
            MODIFY i_vbap FROM wa_vbap TRANSPORTING zzproopdt.
          ENDIF.
Copies the date value in gwa_z1scsp-zzproddt to lv_zzproddt,
if valid date is there in gwa_z1scsp-zzproddt
          PERFORM validate_date USING gwa_z1scsp-zzproddt
                                      lv_zzproddt.
If gwa_z1scsp-zzproddt is not initial then only update in VBEP.
          IF NOT lv_zzproddt IS INITIAL.
            LOOP AT i_vbep INTO wa_vbep FROM lv_index.
              IF wa_vbep-posnr GT wa_vbap-posnr.
                lv_index = sy-tabix.
                EXIT.
              ELSEIF wa_vbep-posnr EQ wa_vbap-posnr.
                wa_vbep-zzproddt = lv_zzproddt.
         Update Original Production date only when its initial.
                IF wa_vbep-zzoprodt IS INITIAL.
                  wa_vbep-zzoprodt = wa_vbep-zzproddt.
                ENDIF.
                MODIFY i_vbep FROM wa_vbep TRANSPORTING zzproddt zzoprodt.
              ENDIF.
              CLEAR wa_vbep.
            ENDLOOP.
          ENDIF.
        ELSE.
Begin of Mod-001
          status = lc_estatus.
          bapi_retn_info-type       = lc_emsgty.
          bapi_retn_info-id         = lc_msg.
          bapi_retn_info-number     = lc_ino.
          bapi_retn_info-message_v1 = gwa_z1scsp-posnr.
        ENDIF.
      ENDLOOP.
       IF sy-subrc EQ 4.
        status = lc_estatus.
        bapi_retn_info-type       = lc_emsgty.
        bapi_retn_info-id         = lc_msg.
        bapi_retn_info-number     = lc_ino.
        bapi_retn_info-message_v1 = gwa_z1scsp-posnr.
      ENDIF.
      CLEAR: wa_vbap, gwa_z1scsp.
    ENDLOOP.
ELSE.
    status = lc_estatus.
    bapi_retn_info-type       = lc_emsgty.
    bapi_retn_info-id         = lc_msg.
    bapi_retn_info-number     = lc_sno.
    bapi_retn_info-message_v1 = gv_vbeln.
    EXIT.
End of Mod-001
ENDIF.
Update the DB tables
    UPDATE vbap FROM TABLE i_vbap.
    UPDATE vbep FROM TABLE i_vbep.
ENDFORM.                    " order_change
*&      Form VALIDATE_DATE
Converts the date into DATS format and check if it is valid,
if valid returns date in p_date_dats else clear it.
     -->p_date_c8    Date in Char format send by SCS
     -->p_date_dats Date in DATS format.
FORM validate_date USING    p_date_c8 TYPE char8
                             p_date_dats TYPE dats.
CLEAR p_date_dats.
p_date_dats = p_date_c8.
CALL FUNCTION 'DATE_CHECK_PLAUSIBILITY'
    EXPORTING
      date                      = p_date_dats
    EXCEPTIONS
      plausibility_check_failed = 1
      OTHERS                    = 2.
check sy-subrc NE 0.
    CLEAR p_date_dats.
ENDFORM.                    " VALIDATE_DATE
*&      Form wf_start
      text
     -->P_IDOC_CONTROL_DOCNUM text
     -->P_GV_VBELN text
     <--P_BAPI_RETN_INFO text
FORM wf_start USING    p_idoc_control_docnum
                        p_gv_vbeln
               CHANGING p_bapi_retn_info TYPE bapiret2.
INCLUDE <cntn01>.
DATA: agents LIKE swhactor OCCURS 1 WITH HEADER LINE,
        process_type TYPE char1,
        idoc_no TYPE edidc-docnum,
        creator LIKE swwwihead-wi_creator.
swc_container wi_container.
swc_create_container wi_container.
swc_set_element wi_container 'Document_no' p_gv_vbeln.
swc_set_element wi_container 'Process_type' '1'.
swc_set_element wi_container 'Idoc_no' p_idoc_control_docnum.
CALL FUNCTION 'SWW_WI_START_SIMPLE'
    EXPORTING
      creator                      = creator
      task                         = 'WS90200019'
    TABLES
      agents                       = agents
      wi_container                 = wi_container
    EXCEPTIONS
      id_not_created               = 1
      read_failed                  = 2
      immediate_start_not_possible = 3
      execution_failed             = 4
      invalid_status               = 5
      OTHERS                       = 6.
IF sy-subrc <> 0.
    p_bapi_retn_info-type   = 'E'.
    p_bapi_retn_info-id = sy-msgid.
    p_bapi_retn_info-number = sy-msgno.
    p_bapi_retn_info-message_v1 = sy-msgv1.
    p_bapi_retn_info-message_v2 = sy-msgv2.
    p_bapi_retn_info-message_v3 = sy-msgv3.
    p_bapi_retn_info-message_v4 = sy-msgv4.
ENDIF.
ENDFORM.                    " wf_start..
The idoc configurations for customized idoc (inbound) are..
1>WE81
2>WE31
3>WE30
4>BD51(Attach ur zfunction mdoule)
5>WE57(Attach ur zfunction mdoule to message type and basic type)
6>we42
7>WE20...
Regards,
nagaraj

MDM Inbound Port Not Processing Files

Dear Experts,
I got an issue while processing file from Ready folder of a specific Inbound Port where files are not processed then i tried with another inbound port of the same repository there it is working fine. Can anybody please help me out to make it work.
Thanks
Ravi

Hi Ravi,
Make sure the user ID that you are using for the auto imports in the mdis.ini file has sufficient rights for that particular port. If thats not there the file would not autoimport.
You could even try importing the file manually using import type as port. This will help you identify if there any problems in the file and its schema that you trying to import.
Also check if the port is set to automatic and the schema and map is maintained correctly.
Another thing that you could check in the console is the port status. If there is a file in the ready folder it must display has data. Or if a file in the exception folder it must then show blocked on exception if you have set that property to yes.
In cases when it does not show if afile present or not,you need to make sure the directory path mentioned in the mdis.ini file is correct. Also you would need to restart the importserver through the services and check again.
If nothing works try deleting the port and recreating it through the console.
Regards,
Aditya Dhurandhar.

Deploy orchestration without inbound port

Hi
I'm using BTDF and I have one biztalk application that have an orchestration that does not have an inbound port. This is
because the orchestration is callable from other orchestrations.
the orhestration however have two way ports that calls and receives info to/from a database.
I have created a bindings, and exported into the masterbinding file.
But when I deploy I get the message: "Could not enlist orchestration "
and the rest of the bindings is not set, I have to manually right click the application,, select configure and manually choose
the ports and host.
So I understand that BTDF cant out-of-the-box deploy orchestrations without inbound ports, but is there a configurational
workaround?
I cannot add an inbound port to that project because then the orchestration won't be callable

Yeah, thats the one ;)
And this is my file.
I created it by deploying the application. Creating the ports I needed, configured everything as it should be. Started the application. Exported the file into PortBindingsMaster.xml
then i replaced some variables with keys that get values from the EnviromentSettings file.
This prosess have worked for all of my applications exept the two without inbound ports
<?xml version="1.0" encoding="utf-8"?>
<BindingInfo xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" Assembly="Microsoft.BizTalk.Deployment, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Version="3.5.1.0" BindingStatus="FullyBound" BoundEndpoints="2" TotalEndpoints="2">
<Timestamp>2014-01-15T14:42:20.8195006+01:00</Timestamp>
<ModuleRefCollection>
<ModuleRef Name="[Application:MeldingsLogger]" Version="" Culture="" PublicKeyToken="" FullName="[Application:MeldingsLogger], Version=, Culture=, PublicKeyToken=">
<Services />
<TrackedSchemas>
<Schema FullName="MeldingsLogger.StorageMessage" RootName="StorageMessage" AssemblyQualifiedName="MeldingsLogger.StorageMessage,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLogger.StorageMessage1" RootName="Ferdig" AssemblyQualifiedName="MeldingsLogger.StorageMessage1,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLogger.StorageMessage1" RootName="FraService" AssemblyQualifiedName="MeldingsLogger.StorageMessage1,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLogger.StorageMessage1" RootName="Guid" AssemblyQualifiedName="MeldingsLogger.StorageMessage1,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLogger.StorageMessage1" RootName="InsertOrUpdate" AssemblyQualifiedName="MeldingsLogger.StorageMessage1,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLogger.StorageMessage1" RootName="Melding" AssemblyQualifiedName="MeldingsLogger.StorageMessage1,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLogger.StorageMessage1" RootName="Tidspunkt" AssemblyQualifiedName="MeldingsLogger.StorageMessage1,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLogger.Sql_Serialization" RootName="anyType" AssemblyQualifiedName="MeldingsLogger.Sql_Serialization,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLogger.Sql_Serialization" RootName="anyURI" AssemblyQualifiedName="MeldingsLogger.Sql_Serialization,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLogger.Sql_Serialization" RootName="base64Binary" AssemblyQualifiedName="MeldingsLogger.Sql_Serialization,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLogger.Sql_Serialization" RootName="boolean" AssemblyQualifiedName="MeldingsLogger.Sql_Serialization,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLogger.Sql_Serialization" RootName="byte" AssemblyQualifiedName="MeldingsLogger.Sql_Serialization,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLogger.Sql_Serialization" RootName="char" AssemblyQualifiedName="MeldingsLogger.Sql_Serialization,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLogger.Sql_Serialization" RootName="dateTime" AssemblyQualifiedName="MeldingsLogger.Sql_Serialization,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLogger.Sql_Serialization" RootName="decimal" AssemblyQualifiedName="MeldingsLogger.Sql_Serialization,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLogger.Sql_Serialization" RootName="double" AssemblyQualifiedName="MeldingsLogger.Sql_Serialization,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLogger.Sql_Serialization" RootName="duration" AssemblyQualifiedName="MeldingsLogger.Sql_Serialization,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLogger.Sql_Serialization" RootName="float" AssemblyQualifiedName="MeldingsLogger.Sql_Serialization,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLogger.Sql_Serialization" RootName="guid" AssemblyQualifiedName="MeldingsLogger.Sql_Serialization,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLogger.Sql_Serialization" RootName="int" AssemblyQualifiedName="MeldingsLogger.Sql_Serialization,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLogger.Sql_Serialization" RootName="long" AssemblyQualifiedName="MeldingsLogger.Sql_Serialization,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLogger.Sql_Serialization" RootName="QName" AssemblyQualifiedName="MeldingsLogger.Sql_Serialization,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLogger.Sql_Serialization" RootName="short" AssemblyQualifiedName="MeldingsLogger.Sql_Serialization,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLogger.Sql_Serialization" RootName="string" AssemblyQualifiedName="MeldingsLogger.Sql_Serialization,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLogger.Sql_Serialization" RootName="unsignedByte" AssemblyQualifiedName="MeldingsLogger.Sql_Serialization,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLogger.Sql_Serialization" RootName="unsignedInt" AssemblyQualifiedName="MeldingsLogger.Sql_Serialization,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLogger.Sql_Serialization" RootName="unsignedLong" AssemblyQualifiedName="MeldingsLogger.Sql_Serialization,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLogger.Sql_Serialization" RootName="unsignedShort" AssemblyQualifiedName="MeldingsLogger.Sql_Serialization,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLogger.Sql_SimpleTypeArray" RootName="ArrayOflong" AssemblyQualifiedName="MeldingsLogger.Sql_SimpleTypeArray,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLogger.Sql_Table_Log" RootName="ArrayOfBatchData" AssemblyQualifiedName="MeldingsLogger.Sql_Table_Log,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLogger.Sql_Table_Log" RootName="ArrayOfBatchMetadata" AssemblyQualifiedName="MeldingsLogger.Sql_Table_Log,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLogger.Sql_Table_Log" RootName="BatchData" AssemblyQualifiedName="MeldingsLogger.Sql_Table_Log,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLogger.Sql_Table_Log" RootName="BatchMetadata" AssemblyQualifiedName="MeldingsLogger.Sql_Table_Log,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLogger.Sql_TableOperation_Log_BatchData" RootName="Insert" AssemblyQualifiedName="MeldingsLogger.Sql_TableOperation_Log_BatchData,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLogger.Sql_TableOperation_Log_BatchData" RootName="InsertResponse" AssemblyQualifiedName="MeldingsLogger.Sql_TableOperation_Log_BatchData,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLogger.Sql_TableOperation_Log_BatchMetadata" RootName="Insert" AssemblyQualifiedName="MeldingsLogger.Sql_TableOperation_Log_BatchMetadata,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLogger.Sql_TableOperation_Log_BatchMetadata" RootName="InsertResponse" AssemblyQualifiedName="MeldingsLogger.Sql_TableOperation_Log_BatchMetadata,MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
<Schema FullName="MeldingsLoggerOrchestrations.Schema1" RootName="Root" AssemblyQualifiedName="MeldingsLoggerOrchestrations.Schema1,MeldingsLoggerOrchestrations, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8" AlwaysTrackAllProperties="false" Description="">
<TrackedPropertyNames />
</Schema>
</TrackedSchemas>
</ModuleRef>
<ModuleRef Name="MeldingsLogger" Version="1.0.0.0" Culture="neutral" PublicKeyToken="9da0d8c7f4d724b8" FullName="MeldingsLogger, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8">
<Services />
<TrackedSchemas />
</ModuleRef>
<ModuleRef Name="MeldingsLoggermapper" Version="1.0.0.0" Culture="neutral" PublicKeyToken="9da0d8c7f4d724b8" FullName="MeldingsLoggermapper, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8">
<Services />
<TrackedSchemas />
</ModuleRef>
<ModuleRef Name="MeldingsLoggerOrchestrations" Version="1.0.0.0" Culture="neutral" PublicKeyToken="9da0d8c7f4d724b8" FullName="MeldingsLoggerOrchestrations, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9da0d8c7f4d724b8">
<Services>
<Service Name="MeldingsLoggerOrchestrations.MessageLoggerOrhestration" State="Started" TrackingOption="ServiceStartEnd MessageSendReceive OrchestrationEvents" Description="">
<Ports>
<Port Name="BatchInsertPort" Modifier="1" BindingOption="1">
<SendPortRef Name="WcfSendPort_SqlAdapterBinding_Multiple_Custom" />
<DistributionListRef xsi:nil="true" />
<ReceivePortRef xsi:nil="true" />
</Port>
<Port Name="BatchMetadataInsertPort" Modifier="1" BindingOption="1">
<SendPortRef Name="WcfSendPort_SqlAdapterBinding_Multiple_Custom" />
<DistributionListRef xsi:nil="true" />
<ReceivePortRef xsi:nil="true" />
</Port>
</Ports>
<Roles />
<Host Name="BizTalkServerApplication" NTGroupName="BizTalk Application Users" Type="1" Trusted="false" />
</Service>
</Services>
<TrackedSchemas />
</ModuleRef>
</ModuleRefCollection>
<SendPortCollection>
<SendPort Name="WcfSendPort_SqlAdapterBinding_Multiple_Custom" IsStatic="true" IsTwoWay="true" BindingOption="1">
<Description>SendPort for SqlAdapterBinding.</Description>
<TransmitPipeline Name="Microsoft.BizTalk.DefaultPipelines.XMLTransmit" FullyQualifiedName="Microsoft.BizTalk.DefaultPipelines.XMLTransmit, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Type="2" TrackingOption="None" Description="" />
<PrimaryTransport>
<Address>${SQL_Server}</Address>
<TransportType Name="WCF-Custom" Capabilities="907" ConfigurationClsid="af081f69-38ca-4d5b-87df-f0344b12557a" />
<TransportTypeData><CustomProps><BindingType vt="8">sqlBinding</BindingType><BindingConfiguration vt="8">&lt;binding name="SqlAdapterBinding" maxConnectionPoolSize="100" encrypt="false" workstationId="" useAmbientTransaction="true" batchSize="20" polledDataAvailableStatement="" pollingStatement="" pollingIntervalInSeconds="30" pollWhileDataFound="false" notificationStatement="" notifyOnListenerStart="true" enableBizTalkCompatibilityMode="true" chunkSize="4194304" inboundOperationType="Polling" useDatabaseNameInXsdNamespace="false" allowIdentityInsert="false" acceptCredentialsInUri="false" enablePerformanceCounters="false" xmlStoredProcedureRootNodeName="" xmlStoredProcedureRootNodeNamespace="" /&gt;</BindingConfiguration><InboundBodyPathExpression vt="8" /><OutboundBodyLocation vt="8">UseBodyElement</OutboundBodyLocation><AffiliateApplicationName vt="8" /><StaticAction vt="8">&lt;BtsActionMapping xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"&gt;
&lt;Operation Name="BatchMetadataInsert" Action="TableOp/Insert/Log/BatchMetadata" /&gt;
&lt;Operation Name="BatchDataInsert" Action="TableOp/Insert/Log/BatchData" /&gt;
&lt;/BtsActionMapping&gt;</StaticAction><ProxyAddress vt="8" /><UserName vt="8">${SQL_UserName}</UserName><InboundBodyLocation vt="8">UseBodyElement</InboundBodyLocation><ProxyUserName vt="8" /><OutboundXmlTemplate vt="8">&lt;bts-msg-body xmlns="http://www.microsoft.com/schemas/bts2007" encoding="xml"/&gt;</OutboundXmlTemplate><PropagateFaultMessage vt="11">-1</PropagateFaultMessage><InboundNodeEncoding vt="8">Xml</InboundNodeEncoding><IsolationLevel vt="8">Serializable</IsolationLevel><Password vt="8">${SQL_Password}</Password><Identity vt="8" /><UseSSO vt="11">0</UseSSO><EnableTransaction vt="11">-1</EnableTransaction></CustomProps></TransportTypeData>
<RetryCount>3</RetryCount>
<RetryInterval>5</RetryInterval>
<ServiceWindowEnabled>false</ServiceWindowEnabled>
<FromTime>2000-01-01T00:00:00</FromTime>
<ToTime>2000-01-01T23:59:59</ToTime>
<Primary>true</Primary>
<OrderedDelivery>false</OrderedDelivery>
<DeliveryNotification>1</DeliveryNotification>
<SendHandler Name="BizTalkServerApplication" HostTrusted="false">
<TransportType Name="WCF-Custom" Capabilities="907" ConfigurationClsid="af081f69-38ca-4d5b-87df-f0344b12557a" />
</SendHandler>
</PrimaryTransport>
<SecondaryTransport>
<Address />
<RetryCount>3</RetryCount>
<RetryInterval>5</RetryInterval>
<ServiceWindowEnabled>false</ServiceWindowEnabled>
<FromTime>2000-01-01T00:00:00</FromTime>
<ToTime>2000-01-01T23:59:59</ToTime>
<Primary>false</Primary>
<OrderedDelivery>false</OrderedDelivery>
<DeliveryNotification>1</DeliveryNotification>
<SendHandler xsi:nil="true" />
</SecondaryTransport>
<ReceivePipeline Name="Microsoft.BizTalk.DefaultPipelines.XMLReceive" FullyQualifiedName="Microsoft.BizTalk.DefaultPipelines.XMLReceive, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Type="1" TrackingOption="None" Description="" />
<ReceivePipelineData xsi:nil="true" />
<Tracking>0</Tracking>
<Filter />
<Transforms />
<InboundTransforms />
<OrderedDelivery>false</OrderedDelivery>
<Priority>5</Priority>
<StopSendingOnFailure>false</StopSendingOnFailure>
<RouteFailedMessage>false</RouteFailedMessage>
<ApplicationName>MeldingsLogger</ApplicationName>
</SendPort>
</SendPortCollection>
<DistributionListCollection />
<ReceivePortCollection />
<PartyCollection xsi:nil="true" />
</BindingInfo>

Sequential message import for MDM inbound ports

Hello,
The scenario is as follows:
PI receives a complex message and split into two simple messages.
These two messages will be sent to two ports of the same repository and insert data into two main tables.
Since there is a lookup main field, one message must be processed by MDIS before the other one.
Would you please suggest an easy way to control this sequential import requirement?
Best regards,
Dale

Hi Dale,
This scenario can be achieved in PI as we can not schedule the inbound ports in MDM (Polling interval is a global attribute in MDIS.INI).
As you are using PI you will be creating two Different Communication Channels for achieving the split and posting it to MDM ports. you can leverage the Functionality " Availablity Time Planning " in Run Time Work bench->Component Monitoring -> Communication Channel Monitoring, where you can schedule(ON/OFF) your communication channels on a specific time periods using the Availability Time as ON TIME from the drop down.
Please find some blogs and links for your reference.
Check Availability time planning
Channel Availability Time Planning
Adapter Scheduling look
/people/shabarish.vijayakumar/blog/2006/11/26/adapter-scheduling--hail-sp-19-
PERIODIC SCHEDULING OF DATA
/people/ganesh.karicharla2/blog/2008/02/08/periodic-scheduling-of-data-between-oracle-db-r3-system
Thanks
Sowseel

Inbound ports blocked now?

I have a few inbound ports open on my router (SSH, SIP, etc) and now for whatever reason I can no longer connect to my services. It appears Verizon is blocking ports. Can anyone confirm this and know how I can have these ports working again. Thanks.
Solved!
Go to Solution.

Working just fine here. Are you sure that your public DHCP address did change and you're trying to connect to the old address? My public IP hops around a couple of times a month.

RSA1 automatically creating port definitions

When setting up BW connection to ECC and SCM systems, RSA1 auto creates port definitions using the generated A000000X format. I want to use a predinfed port like BIQ100 or BIP100 (source client format).
Is there a way to use predinfed versus generated port defintion.
Thanks
Jexun

Go to transaction WE20 and maintain the port in the outbound parameter in the correct logical system under partner type LS.

Transfer ports definitions between SAP systems

Hi,
I would like to know if there is a way to transfer ports definitions (WE21) between SAP systems ?
Thanks, Nir.

There is no program to copy ports into another system. You could write an ABAP program and an RFC FM to read EDIPOA and EDIPORT tables from other client and insert them into the current system tables, but it is not suggested to do that because the RFC destinations should exist and no company wants to do direct update on SAP delivered tables because SAP will not support in case of errors.
Thats why as far as my experience, I've always created them manually.
regards
Shravan

ORA-24816 Error on EDI inbound processing

We are encountering an issue for EDI X12 inbound data files which have extraneous characters. B2B initially failed throwing “ Document Protocol Identification error “ .
To resolve this, we enabled flag “b2b.edi.enablePeprocess” to true , after which it started processing fine in DEV environment , however it throws below exception in QA environment .
Internal Exception: java.sql.SQLException: ORA-24816: Expanded non LONG bind data supplied after actual LONG or LOB column
Error Code: 24816
Call: INSERT INTO B2B_WIRE_MESSAGE (ID, JOB_ID, ACKNOWLEDGEMENT_MODE, LABEL, ATTRIBUTE2, MESSAGE_DIGEST, ATTRIBUTE4, MESSAGE_ID, ATTRIBUTE3, ATTRIBUTE5, CPST_INST_CREATED_TIME, CREATED, LAST_RESUBMITTED_TIME_STAMP, MODIFIED, LAST_VIEWED_TIME_STAMP, MSG_SIZE, DELIVERED_ENDPOINT, PASSWORD, DIRECTION, PORT, ENCRYPTION_CERTIFICATE, PROTOCOL_COLLABORATION_ID, ERROR_CODE, PROTOCOL_MESSAGE_ID, ERROR_DESCRIPTION_CLOB, PROTOCOL_TRANSPORT_BINDING, ERROR_TEXT_CLOB, REFER_TO_PROTOCOL_MESSAGE_ID, EXCHANGE_REMAINING_RETRY, RESUBMIT_COUNT, FROM_ADDRESS, SIGNING_ALGORITHM, SIGNING_CERTIFICATE, MESSAGE_STATUS, SIGNING_PROTOCOL, LAST_VIEWED_USER_NAME, STATE, DIGEST_ALGORITHM, TO_ADDRESS, ENCRYPTION_PROTOCOL, TRANSPORT_CERTIFICATES, ERROR_TEXT, TRANSPORT_CORRELATION_ID, EXCHANGE_RETRY_INTERVAL, TRANSPORT_HEADERS, ATTRIBUTE1, TRANSPORT_PROTOCOL, CHANNEL_NAME, TRANSPORT_PROTOCOL_VERSION, ERROR_DESCRIPTION, TRANS_SECURITY_PROTOCOL, HOST_NAME, TRANS_SECURITY_PROT_VERSION, ENCRYPTION_ALGORITHM, URL, LAST_RESUBMITTED_USER_NAME, USER_NAME, EXCHANGE_ATTEMPT_COUNT, VERSION, PAYLOAD_STORAGE, PACKED_MESSAGE, RESUBMIT_REF_TO) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
bind => [A513532C140185965980000010261DFC, null, SYNC, null, null, rLdBG4pYQf76lQXJZdl43gE7QqE=^M
We checked many options for the differences between Dev & QA , but could not find a root cause .
Version : 11.1.1.6

Hi,
I am getting the same error.
Can u please help me on this.
Thanks and Regards
Neha Kapoor

Status 56 : EDI Inbound Partner Profile not available

I am trying to load an inbound 856 IDoc from EdI subsystem to SAP. It si giving me an error 56 saying Inbound partner profile not available.
I have set up the partner as Vendor in we20. Is there any other place that I need to set up the partner. We have inbound docs coming in as a customer(KU) but this is first vendor set up
Do you know what I am missing?
When I clicked on status message 56 -- says /ICPLPLIVA/LI/LF/DESADV///T/....key fields missing in EDP21? is the error really meant that?
Thanks in advance

Hi,
Can you tell us about the IDoc control record?
In order to determine whether need to setup LI or KU partner profile.
Please go to WE02 and check the IDoc control record.
What are the values in partner tab?
Port             ???
Partner number   ???
Partn.Type       ???
Function
Port             ???
Partner number   ???
Partn.Type       ???
Partner Role
Regards,
Ferry Lianto

EDI Inbound-Port definition

Similar Messages

Maybe you are looking for