Inbound delivery partner profile question

Hello,
Based on the help documentation, i have setup a distribution model between ECC and EWM system.
After executing this transaction /n/SPE/OL19, my distribution model is properly generated and I am able to send Idoc from ECC system. However on on EWM system, I am getting an error related to message type DELINF is not found in inbound partner profile.
I searched in WE80 and I do not see this message type in SCM system, can someone kindly suggest if the below mentioned message types used in ECC are right and on the SCM side I have only one message type which is SYNCH.
Following message type in ECC
DELINF
DELORD
/SPE/LIKP.DELIVERYCHANGE
/SPE/LIKP.REQUESTCHANGES
/SPE/LIKP.SAVEREPLICA
BUS2015.DELIVERYCHANGE
BUS2015.SAVEREPLICA
BUS6050.EXECUTE
Following message type in SCM
SYNCH.
Am i missing some setting which is preventing from idoc to be posted in EWM to generate inbound delivery request.
If someone could suggest what are the message types should exist for inbound in EWM side or DELINF needs to be added in EWM system.
Appreciate your suggestions/comments.
Thanks
Bhaskar

No..you can not know it.There is no log.

Similar Messages

IDOC question on Message type and Basic Type - Partner Profile

Hi all,
I am wonder if I can post any IDoc question in this right forum/module. If not please direct me to the right forum/module. I am a newbie in IDOC setup.
My question is about the setup of Partner Profile creation (WE20).
When creating a new partner, for example with partner type LI, I notice there is outbound parameter and inbound parameter.
Questions:
1 u2013 It makes sense to have only one message type record appear in EITHER one of these two tables. I notice that some partner in my system has message type record exist on both the inbound and outbound parameters table, why system allows? What is the business rational?
2 u2013 May I have a list of standard SAPu2019s Message Type object of its usage description, and its allowable Basic Type (ie. IDOC TYPE). Basically a website to describe their (i.e. Message type and its Basic Type) business usage.
Thanks.
tuff

Tuff,
Below are my thoughts,
There is a partner sing partner type LI. This partner in the WE20, has one record (i.e. with Message Type ORDERS) exist in the Outbound Parameter table. This partner also has 4 records (i.w. with Message Type DESADV, INVOIC, MBGMCR, and ORDRSP) exist in the Inbound Parameter table. So my question is what is the business rational behind this kind of setup. Because I am confuse when come to create a partner profile, whether I need to create a message type in Inbound Parameter table or Outbound Parameter table, or I need both.
OK, so looking at the above example, you have an orders message type(This is for creating an order) in the outbound, this means that you are sending out an IDOC(purchase order for ex) to this partner, so that this partner can create an SO in his system and fulfill your order.
Now you also, mention that you have other four Message types for the same partner on the inbound, now let us look at the above scenario, you have asked your partner to fulfill the order, i guess you would like to get a confirmation from him/her if the order was created or not in his/her system and how and when is he/she going to fulfill your order requirement. This he/she does by sending an response to your order - ORDRSP.
And when the partner is ready to ship your order to you, he/she sends out a Advance Shipping Notice - ASN via the IDOC of message type DESADV.
Finally and most importantly , he/she will send you the invoice - INVOIC for the order.
In general, you interact with your partner via Business Docs - Order, Delivery, ASN, Invoice etc, so whatever document come from your partner - ORDRSP, INVOIC etc will be on the inbound profile of the partner. Whatever docs that you send ORDERS, ORDCHG etc etc will be on the outbound profile of the partner.
2 - Bascially I would like a reference in any website that allow me to choose which message type is best use for my partner profile, so that I don't have to reinvent.
Well, there is no choice of choosing/best message type for a given requirement - So for sending an Invoice the message type is INVOIC, ORDERS - For order creation, ORDCHG for order change etc. However the IDOC type, is some thing that you can choose, for Ex: ORDERS01 - ORDERS05, these are the IDOC types that are available, so if you are interacting with a partner who are running an old version of SAP and their system has only upto ORDERS02 in their version of SAP then you would use ORDERS02.
Regards,
Chen

Partner profile for INBOUND IDOC

Dear experts,
Need your help to define partner profile for inbound idoc to R/3 system. There is a third party (Non SAP) based application from which idocs need to be sent to the R/3 system. There is no need to send an outbound idoc from the R/3 system. Can some one please suggest what are the steps to be taken to b configure the partner profile in the R/3 system for the inbound idoc?
Thanks,
Priyanka

Hi
This is not the right location to post this question.
You got to post this query in Data transfers section of SDN ABAP Development forums
Now regarding your question,
You need to create a Logical System with the help of the transaction SALE.
Assign the created LS to the client with the help of same transaction
Go to WE20 and create the partner with the same Logical System name
Now..as you are recieving the Inbound Idoc from external Non-SAP System, you need to maintain the message type in the Inbound Parameters by clicking on ADD Icon over there.
Before doing the above step, you got to create the connection between SAP and Non-SAP System.
Use transaction SM59 to do this. Type of connection would be R/3 I guess
Thanks
Hope it helps.

File2Idoc - Error [EDI: Partner profile inbound not available]

Hi All,
I am executing file to Idoc Scenario, It is picking the file from sender & delivering to Idoc as well (fields) in R/3 system and showing chequered flag SXMB_MONI.
But If go to WE02 in R/3 : It is showing that Partner Profile not availbe , I have already mentioned in We20 - R/3 system.
EDI: Partner profile inbound not available
Diagnosis
An inbound partner profile could not be found with the following key:
I checked in Idoc - Control Segments - > It is shwoing Wrong recipient Partner No & Type
Recipient Information :-
Partner No - CLNT_300              Expecting   100008
Partner Type - LS                       Expecting     LI
Where are to maintain these entries ?
Please do the needful.
Regards,
~Anshul

Sandeep,
I am using simple Idoc Delivery:-
Idoc:DELINF.DELVRY05      Messgae Type u2013 DELINF     Process Code -- DELV
But I am getting error in R/3 - WE02
I checked in all entries in We20
EDI: Partner profile inbound not available
Message no. E0337
Diagnosis
An inbound partner profile could not be found with the following key:
/PEVCLNT100/LS//DELINF////
This involves the key fields of table EDP21:
-SNDPRN partner number of sender
-SNDPRT partner type of sender
-SNDPFC partner function of sender
-MESTYP logical message type
-MESCOD logical message code
-MESFCT logical message function
-TEST    test flag
Thanks,
Anshul

Partner profile of output type equal LS (To a delivery)

Hi,
I want to generate an idoc every time that a delivery is created on the basis of the condition (Shipping point=xxx,delivery type = yyy, loading point = zzz)
So I'm trying to define a logical system (One logical system by default) as partner profile to my output type.
So in transaction V/34, I put that the output type has to be a LS via EDI.
And in transaction VV21 I defined that the LS 'LSYS' has to be my partner by default.
But in my delivery. In the output type header, It's saying that my logical system 'LSYS' isn't a Partner.
What should I do in order to have a logical system as a partner in my delivery.
Thanks in advance

You cannot have a LS as partner in a SD document.
You have to define a partenr definition for each ship-to you use in WE20, and set the right output message in it.
reward points if helpful, pls.
regards
Roberto

IDoc Receiver, Error in we02 - EDI: Partner profile inbound not available

Hi All,
I have a problem when creating a receiver IDoc from XI to R/3.
I have successfully tested the IDoc when populating the receiver information from the payload. However I want this information to be populated automatically based on the logical systems.
When I do this I get the following error in the IDoc in R/3:
EDI: Partner profile inbound not available
In the control record the sender information is all correct but in the recipient information the partner Number with type LS is populated, but port is not populated.
I have done the following steps.
     the sender is a Business Service so I have created a logical system directly adapter-specific identifiers in the sender service in the integration directory.
     In the receiver business system I have imported the logical system into the adapter-specific identifiers in the ID from that specified in the SLD.
     In the receiving R/3 system using SALE/BD54 I have created a logical system for the source system.
     In the receiving R/3 system using we20 I have created a partner profile of type LS with the same name as the source logical system.
     IN PI/XI system in transaction IDX1 Ive created a port (SAP<SID> where <SID> is the system ID of the receiving R/3 system) and the client of the R/3 system, and the RFC destination of that system (<SID>CLNT<clnt>, as specified in SM59).
     In the IDOC Adapter (receiver) I have entered the RFC destination and port matching those created above. All checkboxes are UN-checked eg. take sender from payload, take receiver from payload, Apply control record values from payload, etc. are all NOT checked.
I think that Ive done everything correctly, but I get the error in we02 in R/3: EDI: Partner profile inbound not available.
Any help will be greatly appreciated (and rewarded, obviously).
Thanks,
Matt.

HI Matt,
Can you please copy paste the exact error message....In your error message it will show you Exact partner Number / Logical System name and other parameters...just compared if you have all parameters set in your partner profile comparing to error message...
If you can giev screen shot of both..then probably would be easy to point out error.
Hope this will help.
Nilesh

Inbound EDI multiple customers using 1 partner profile

I would think that it's possible to set up a single partner profile in WE20 through which you can process multiple idocs against multiple customers for order processing. Can anyone guide me on how to achieve this.
Thanks, Mart

Absolutely. You could have an EDI Partner called 'GENERIC' for example, and could use that to process inbound EDI Sales Orders. Obviously you would need an identifier to represent the correct Customer account, ideally this would be the Sold-to number. If it's not your Internal Sold-to, but another unique number, then you should be able to add mapping via transaction VOE4 to table EDPAR. I.e the Customers sends an external number 123 representing their Store Id, you map that back to your internal Customer Number. Only trouble with this is if two different Customers had the same external Id, as you would have no control over that. For our generic EDI Partners, the Customer Number is mandatory.
Cheers, Paul.

Partner not copied from Purchase order to inbound delivery

Hello,
When I create an inbound delivery (VL31N) from a purchase order (ME23N), the partner FM is not copied (whereas partner FO is copied).
Does someone know how to solve this issue? (customizing or user exit..).
thanks

Hi,
Is there any specific Copy Control Routine or User Exit that copy Partners from a Purchase Order Header to Delivery Header?
Please provide me the Routine Name/Number or User Exit Name.
Thanks,
RV

Invoice EDI error : EDI: Partner profile inbound not available

Hi EDI experts ,
We are connecting our SAP ECC 6 ( Ehp 4) system to 3rd party system Mincom via SAP PI, to send PO Creation message (Outbound) and receive Vendor Invoice message( inbound). We already done all the settings..Output determination procedure, Partner Profile ( WE20) , Port creation , Condition Records, EDI settings in SPRO for invoice..etc as below:
Logical system ( BD54)
ECC system - EDACLNT112,
PI systems u2013 IDACLNT210
Third party u2013 LSMINCOM
Port ( WE21)
IDACLNT510 : For PI with RFC destination IDACLNT510
Partner ( WE20)
LSMINCOM : (Partn.Type LS)
Outbound parmtrs.- Partner Role- LS, Message : ORDERS , Port - IDACLNT510
Inbound parmtrs.- Partner Role- LS, Message : INVOIC , Message Variant- MM, Process code u2013 INVL, Trigger immediately (Process code INVL have Identification - IDOC_INPUT_INVOIC_MRM, Option ALE u2013 Processing with ALE services , Processing type- processing by functional module)
Here PO Creation is working fine . IDoC of PO outbound message have below details :
Recipient information:
Port :     IDACLNT510 (Logical system & Port created in WE21 )
Partner Number : LSMINCOM   ( Logical system and Partner created in WE20)
Partn.Type : LS
Function : LS
Sender information:
Port : SAPEDA ( donu2019t know how it created..but in WE21..it is not there)
Partner number:   EDACLNT112 ( Logical system and Partner created in WE20)
Partn.Type : LS
Partner Role :Blank
Just started testing, our PI team is sending the IDoC, with wrong information on partner & other data, so inbound IDoC failing with error u201CEDI: Partner profile not availableu201D. Oaky. I reprocessed these failed IDoCs by changing Partner data just opposite (i.e. Sender info as Recipient info & vice versa) to successful PO Creation O/B message in WE19 in EDIDC and when I click on u201CStandard Inboundu201D, then another window open giving error message u201CPartner profile not maintainedu201D and creates new IDoC with status 56
EDI: Partner profile inbound not availableMessage no. E0337
Diagnosis
An inbound partner profile could not be found with the following key:
/LSMINCOM/LS//INVOIC///X/
This involves the key fields of table EDP21:
-SNDPRN partner number of sender
-SNDPRT partner type of sender
-SNDPFC partner function of sender
-MESTYP logical message type
-MESCOD logical message code
-MESFCT logical message function
-TEST    test flag
Procedure
Please check the inbound partner profiles.
Execute function
I am not getting exactly what inbound partner profile could not be found or what is the problem here . Can anyone suggest me what should be the problem and solution on it ?
Thanks
NAP

Narendra,
Please advice what was the solution.

Partner Function for STO and relevant inbound delivery

Dear Expert,
i did the partner configuration for Vendor and STO with partner VN-vendor DP-delivery plant.
When i create the STO vendor UP07, both of VN and DP are UP07, but when i create the STO for UP07, no partner data come out for the PO, the partner data didn't copy out from vendor master.For standard PO not STO, the partner data are copied from vendor master automatically. Any advice any further more setting need to do?
I manually input the partner data for the STO, then i try to create inbound delivery, following incompleteness came out"Vendor : Account Number of Vendor or Creditor Missing",user need to manually input the partner number for LF-vendor.But when i check the partner setting for inbound delivery, LF is copied out from VN.Any more setting need to do to make sure the partner number of LF is auto copied from PO data.
Look forward to your reply,
Thank you and regards

Hello,
PLease check the vendor data created as a plant. Go to Vendor master and in purchasing view select extras -> additional Purchasing data-> in the plant assignment enter the Plant number. This will pull in the vendor details into the inbound delivery.
Thanks!!

Partner in inbound delivery

Hi,
I'm creating an inbound delivery with trx VL31N, I clicked on header button, then I clicked the Partner tab
and if I click on Propose alternatives button the system prompts *There are no alternatives available for Vendor
X*.
I want the system proposes automatically the partner number when I click on Propose alternatives button
Regards

Have you maintained these settings?
SPROLOGISTICS EXECUTIONSHIPPINGBASIC SHIPPING FUNCTIONSPARTNERS--SET UP PARTNER DETERMINATION FOR DELIVERIES
Here, select the procedure for inbound deliveries, and add your partner.
Then maintain the partner number in vendor master data.i.e. this partner needs to be added as a partner function in vendor master also.

EDI: Partner profile inbound not available Message no. E0337

Hi Friends,
I am facing very wiered issue for incoming vendor frieght invoice. When the IDOC is sent to SAP from the edi subsystem, it gets posted with status 56 and error message
EDI: Partner profile inbound not available
Message no. E0337
Diagnosis
An inbound partner profile could not be found with the following key:
/0040000010/LI/VN/INVOIC/MM///
This involves the key fields of table EDP21:
-SNDPRN partner number of sender
-SNDPRT partner type of sender
-SNDPFC partner function of sender
-MESTYP logical message type
-MESCOD logical message code
-MESFCT logical message function
-TEST test flag
I have created the partner profile in WE20 for Partner type LI, partner role VN and process code INVL, message type INVOIC, message code MM. I have also checked the entry in TABLE EDP21 and the entry exists.
When I open the IDOC in WE19, and click on standard inbound TAB it says partner profile not maintianed, however when i click on the control record it opens a dialog box, where we have all the entries for partner profile and when I just click on any field in the dialog box and click continue and when again click on standard inbound it say partner profile maintained.
None of the data is changed in the IDOC control record, I just click on any field and it finds the partner profile.
Please let me know your thoughts, what could be possible reason and a solution.
Thanks
Deepak

Hi Deepak,
I am facing the same problem with a different message type.
But same effect. I can copy the IDoc with WE19 and it will process nicely, completely unchanged.
Have you found the reason for this?
Thanks,
Florian

Inbound Idoc processing issues - Partner Profiles - error status 56

Hello All,
I'm having a little difficulty posting an idoc coming from MDM. It's a CREMDM04 xml coming from an MDM system. It is getting mapped through PI and is being split into ADRMAS02 and CREMAS04 Idocs. The message is being passed through XI and being posted to the ECC system, but certain fields in the EDI_DC40 header table are not being populated correctly (i believe). I'm using nothing but standard mapping/material from the SAP Business Content for XI. After looking through the standard XSLTs i cannot find the field-to-field mapping where the fields below are being populated.
The RCVPOR value (SAP[SID]) is correct when i view it in SOAP Header, but does not appear in the remote system under the receiver port for the inbound idoc.
The RCVPRN value ([String Value]) is incorrect in the SOAP Header and does appear in the remote system under the receiver partner number for the inbound idoc. How is the RCVPRN value being populated?
SOAP Header in IDocOutbound tag
<SAP:RCVPOR>SAP[SID]</SAP:RCVPOR>
<SAP:RCVPRN>[String Value]</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
I've been trying to trace down the string value for the RCVPRN, but i cannot find it anywhere. Perhaps i'm just overlooking it?
When i set the proper values (port = SAP<SIDofECC> and partner number = <LSnameof ECC>) using WE19 in the remote system then the partner profile is found and i'm left with different error to please specify an address group.
Any help is very much appreciated! :-D

Hi Jason ,
Just check out if you have done the following steps most of us make minor mistake here ....... I think this would solve your problem
To Configure the IDOC SCENARIOS ,PROCEED AS FOLLOWS
STEP 1:ALE SETTINGS TO POST IDOC INTO SAP R/3
We need to do the following settings in XI
1) Create an RFC Destination to the Receiving 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 XI towards R/3
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 Inbound 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 Inbound Parameters.So click on ADD TO Create Inbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Message Type and Process Code.
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
do let me know if it helped
Edited by: Tom Jose on Feb 21, 2008 9:04 AM

Delivery split through VLSP along with JIT Calls with AW Partner profiles

Hi SAP SD/LE Guru's,
I have one critical issue to resolve immediately in my implementation of SAP 4.6C system in multinational automotive industry. It's in the area of Delivery split along with AW - Duns number partner profile and JIT calls.
Here is the scenario:
1. JIT(Just In time) calls will be created through EDI based on the ship-to, PO Nos, Duns number.
2. The requirements will be updated in Scheduling Agreements JIT Delivery schedule.
3. Picking is done based on the requirements.
4. Packing, Deliveries and Handling units are created: Note: Each handling unit is linked to one JIT Call.
5. Based on the Shipments, Deliveries needs to be split into further sub-deliveries.
Ex. One Delivery has two HU's. This needs to be split into another delivery so that one HU need to be detached from original and attach to new delivery. At the same time corresponding JIT call also need to be detached from original delivery and attach to new delivery. This can be done through VLSP : Subsequent split(Outbound delivery). Split profile: 003 - split based on Quantities.
The issue: When executing delivery split using VLSP and split profile: 003, the system is terminating and giving short dump.
The error analysis says that AW - Duns number is creating the problem. The short dump occurs in SAPLV05I in Function module: SD_PARTNER_UPDATE.
There is an SAP note: 154766 related to this problem says that Partner header should be used only once in copy control.
But in customization of copy control from Sales order to Delivery, there is no VBPA Partner header.
I appreciate if you can provide solution for delivery split and resolve this short dump issue.
Thanks,
Murali Chintakunta

In reference to this change in the Custom Reports... Better experience when exporting data - to prevent customer confusion when exporting data from Mac computers, we have removed the export to excel option and exporting in CSV format by default.
What is the customer confusion we are trying to stop here? I've got even more confused customers at the moment because all of a sudden they can't find the export to excel option but know it exists if they log in on a PC?
Mark

Copy partner from PO to inbound delivery

Hi! I have create new partner function called FA and am able to maintain with other partner functions such as CR for the vendor master. When I create the PO, these partners are copied to the PO. However, when I create an inbound delivery for the PO, only CR is copied over but not FA. I have checked the configuration but couldn't find anything wrong with the set up. Does anyone know whether standard SAP can be configured to copy all the partners over? Have I missed out a config?
Thanks
Dilip

I'm also having the same problem but after looking into the source code it is not possible to copy another partner different than LF (Vendor) to the inbound delivery with customization. A user exit or a BADI will be necessary.
I have an explanation if you're interested in technical details:
When an inbound delivery is created, the partners are determined in
FM SHP_COPY_PARTNER_FROM_PREC_DOC
FORM FILL_VBPA_SINGLE.
There you'll see that the code only handles the following partners WE(SH)Ship to party, AG(SP) Sold to party, LF(VN) Vendor and SP(CR) forwarding agent.
Previous to this, program RM06EANL (called by txn VL34), field LIFNR is the only field filled in structure XKOMDLGN. Field SPDNR is not filled at all, in this way, there is no chance that even forwarding agent gets copied in the function described in the previous paragraph.
pd: The system gives all parameters for creating an inbound delivery into structure XKOMDLGN and executing FM RV_DELIVERY_CREATE.
Regards.
[ivo]

Inbound delivery partner profile question

Similar Messages

Maybe you are looking for