RECEIVING PARTNER DESCRIPTION

Hi all,
I need to create a custom table with the following fields: sold to, sold to description, EDI partner type, partner number, and partner description. My problem is where to retrieve the partner description if the partner type is equal to B (bank), BP (benefits provider), GP (business partner), LS (logical system), and US (User). I understand that if i input a partner type KU or LI, i can get the description at table KNA1 and LFA1. But for the other partner types, i don't know on where to retrieve the description.
Please advice on what table i will retrieve the description.
Thanks a lot!
Jim

HI Jim ,
TEDST, TEDTT tables
FOR PARTNERS , Check the table TEDST-RCVPRT B,BP,KU,LI,LS,US
FOR DESCRIPTIONS
TEDTT-DESCRP " FOR DESCRIPTIONS
u ll get the info here ..
Cheers
VijaySimha .

Similar Messages

Receiver partner type in control record is default"

Hi all,
I am Getting 56 Error"Receiver partner type in control record is default".
When I go to that perticular IDoc under control record under parter tab I am providing "PARTNER TYP" AND PORT.When I save these details th idoc is getting posted.
The port ifo is present in we21.I checked RFC Destination,It is fine.
Now where to give this information centrally since I have to manually enter this every time.
Thanks,
SrinivasaP

Hi,
If error is 56.
Check the partner profile is created or not, if not create partner profile, restart the process by TA.BD87.
If partner profile is exist then check the control information in the IDoc file is incorrect. Correct the IDoc file and restart the process
Please check receiver IDoc Adapter is configured with the said details are not.
And if possible map the values in EDI_DC40 control record.then you need not to give these details every time.
Regards
Chilla..

IDoc receiver AEE: Error "Configuration for Sender/Receiver Partner Number/Port is incorrect"

Hi all,
We are on PI 7.4 AEX SP 7. We are trying to get the following scenario working: Inhouse warehouse management system (JMS) --> PI --> ECC (IDoc)
Sender is configured as 3rd party technical system system with business system maintained in SLD
business system has logical system assigned in SLD
adapter specific identifiers show logical system in ID / NWDS
logical system is defined in receiver (ECC system)
partner profile is created in ecc for this very logical system (inbound parameters)
No mapping of EDI_DC40 node in ESB (complete node disabled)
no header mapping in ID / NWDS
receiver IDoc AEE adapter is configured to not enforce control record (Control Record in IDoc XML = Not Mandatory)
no Identifiers specified in receiver IDoc AEE adapter
My guts feeling is that this should work, however, it doesnt't. Failing with "The Configuration for Sender/Receiver Partner Number/Port is incorrect. Enter proper values in Sender/Receiver Component"
Any thoughts are highly welcome.
Cheers
Jens

Hi,
The error mentioned by you is not related to the port..but its related to the Application ...
IDoc 51 means idoc has been received in R/3 client and when it tries to process it ended in error..
Check with the functional consultant for the error you have received..
HTH
Rajesh

Sender and receiver partner number,

Hi All,
In the control section of an idoc, there are two fields - sender and receiver partner number. If my application sends an inbound idoc to Sap R/3, the two fields are not necessary? I have noticed the logical system has been assigned to the client.
If somebody can explain the usage of sender and receiver partner, I would be much appreciated.
Thanks,
Dennis

Hello,
Can you please check the documentation: SAPBCSapAdapterGuide in your packges -> SAP -> Doc direcotry? The Chapter: 6
This should explain you how to set up the Routing.
Best regards,
Dezso

ERROR:Receiver Partner record in the control record is default

Hi,
When I am trying with WS t Idoc scenario the followinw error is getting
"Receiver Partner record in the control record is default" when I am checking in we05
Please clarify.
Thanks,
Srinivas

Hi,
Check the partner profile settings in we20.
Regards,
Smitha.

IDOC sender/receiver partner type LS?

Hi,
I am in need of advise if SAP 5.0 can be configured for ORDERS outbound (PO NEU) to pick up receiver (KU) partner type by standard config?
I understand that there's exit available but would like to utilise standard application config method.
Regards,
Viv
will definitely award points for the help!!

if i understood u right this might help you
1. /people/shabarish.vijayakumar/blog/2006/09/13/wanna-party
2. https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660

56 error,EDI: Receiver partner type in control record is default

Hi all,
When I trying to post the IDOC the 56 error is shown.
I checked the partner profiles and found fine.Please clarify.
Thanks,
Srinivasa

Hi,
this means that your IDOC has some errors
you can see it by clicking on the status in We02
then you will know exactly where the error is located
in inbound processing you should see status 53 - successful
BTW
to check IDOC errros with XI:
/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi
Regards,
michal

Changing the receiving partner in idoc (Outbound SALES ORDER)

Hi All,
In my scenario Sales order (ORDERS) outbound is created and it should send to Delivering plant not to the Sold-to party. how to do this in partner profile? Is there is any coding should be written?
Thank you in advance,
Adithan S.

Hi,
Aveek is right, you only option is to use partner type 'LS'. So you need to create logical systems for these delivering plants, but since setting up 'LS' as the partner function for all the customers requires lots of illogical customizing changes and master data changes, I suggest that you use 'ALE' medium instead of 'EDI'. So that all you need to do is maintain distribution module for any one of these logical system so that output type processing can take place. Later you can use exit 'EXIT_SAPLVEDC_001' to change control record (change recipient to delivery plant).
Cheers,
Sanjeev

Error is Receiver AS2 adaptor used for Idoc to AS2 scenario

Hello Experts,
   I am doing Idoc to AS2 B2B scenario where I am getting below error message in runtime workbench comm channel monitoring.
Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: AS2 Adapter failure # Outbound configuration error: Sender configuration incomplete - perhaps AS2ID missing.., SEEBURGER AS2: AS2 Adapter failure # Outbound configuration error: Sender configuration incomplete - perhaps AS2ID missing..
Sending failed.
Error type: COMPONENT_ERROR,NOT_TRANSMITTED >> Error date: 10/16/09 9:06 AM >> Description: AS2 Adapter failure Outbound configuration error: Sender configuration incomplete - perhaps AS2ID missing.. com.seeburger.as2.AS2Plugin.execute(AS2Plugin.java:321)
AS2 Adapter failure
Processing task
Sending called.
Message processing started
Basis has already configured the AS2 Server with Certificates and provided me the below details for receiver agreement and those are put in Receiver agreement.
AS2 sender Configuration:
Authentication certificate à TRUSTEDAS2certAS2_datapool
AS2 Receiver Configuration:
Decryption Key à TRUSTEDAS2certXXXenterprise2008
Signing Key à TRUSTEDAS2certXXXenterprise2008
XXX is my receiver partner
For the Receiver party XXX I have maintained the Identifier as given below
*Agency----
Scheme-------Name*
http://sap.com/xi/XI--XIParty--
XXX
Seeburger----
AS2ID----
XXX_AS2ID
There is no need for sender agreement for Sender IDoc but still I tried to created R3 as sender party and R3 Business system, used it for the scenario and created sender agreement for sender Idoc but received same error message in Runtime workbench.
R2 system sender party is also set with identifier with AS2 ID.
MDN mode is set to no MDN in the receiver AS2 communication channel.
Please suggest me if something is missing or wrong in the configuration.
Thanks in advance.
Vinit

Hi Larry,
   The solution was very simple.
It was problem with the basic understanding of system and configuration.
Idoc is send sent by R3 ERP system and target is Partner Party. As ERP system is Business system and not the party w.r.t XI/PI terminology, we are not supposed to use Sender party as Sender ERP system but just use Business system as sender without any sender party. So in this way PI system could recognize that the data is coming from R3 system which is nothing but PI Business system.
Now question comes where to user the Serder Party which was defined with AS2 ID? So answer is in the receiver determination we have to mention the Sender party and sender service in the header mapping part (Also mention receiver party and service).
So in my case problem was with sernder party. I mentioned sender party in all receiver determination, Interface determination, Sender Agreement and receiver agreement where only sender service ie sender system was required. And as I configured my scenario without sender party it worked because PI could recognize the sender R3 system and AS2 ID was recognized form the Header mapping of Receiver Agreement.
Kindly let me know if it works and if you require snap shots of my configuration then I can send you the same.
Regards,
Vinit

Special stock partner data problem in ERP system during "Post Goods issue"

Hi all,
I have a (probably) customizing issue in an ERP 6.0 EhP4 test system which not occurs in the ERP 6.0 test system. There is a difference but no one could tell me, what causes the problem in this scenario:
I have two customers, C1 and C2. C2 is the special stock partner (SB) of C1.
I've created a Consignment Fill-up order, then a delivery document based on the order and posted it with "Post Goods Issue". During the update process, a function module (SD_PARTNER_UPDATE) receives partner data in an internal table which contains the sold-to, ship-to and special partner data.
When we tried the same process in the ERP 6.0 EhP4 test system then special-partner data did not occur in the parameter table (I've used the same customers and materials). The special stock partner is probably not taken into consideration due to some customizing settings.
My question is what should I change in the customization to run the process the same way as in the ERP 6.0 system? As far as I know there are no new modifications which have effect on this area, and the used test customers and materials are almost the same - there are no noticable differences.
Thanks in advance.
Akos

I tried setting that field in the sale order this morning. By defaulting it to "C"; I was able to get warning message for TAE line. I was able to post goods with TAE and TAQ, being different quantities. I need the check to determine if TAE and TAQ delivery quantity are different. Using this fields seems to be line specific. Thanks for the suggestion. I now know what that field does to the delivery.
I rewarded points.
Thanks,
Tony

File to IDOC - issue with partner profile

I have done File to IDOC scenario and tested it end to end successfully. For same have done all require configuration setting in R/3 like defining logical System and partner profile. And it sends new IDOC successfully in R/3 with status code 50 (IDoc added).
But when I create new logical system and partner profile in R/3 and when I use same logical system in my above mention scenario then my new generate IDOC in R/3 return status code 56 (EDI: Partner profile inbound not available). But same scenario work fine with my earlier partner profile. Here I have done all require changes at adapter level like adapter specific identification and same new logical system I have update in SLD with my business system Logical System Name.

Hi Bhavesh,
Thanks for your reply.
In control record, I checked with sender and receiver partner. In this sender partner is new partner profile which I have created with port details. Receiver partner has logical system name which I have mentioned in my SLD for my receiver business system. But in receiver partner dont have any port details.
But still it has same problem.
-Sunil

Error in receiver IDOC_AAE

Hi Exparts,
I am using PI 7.3. I have configured receiver IDOC_AAE as per the thread http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/21717. [original link is broken] [original link is broken] [original link is broken] But if I check controll record from payload option then IDOC is created properly. But if I don't check that option I am getting the error "IDOC adapter exception.sender/receiver partner,port is incorrect. enter proper values in sender/receiver component", in RWB as ontroll records are not getting populated automatically from config just like ABAP based IDOC adapter. Please share your knowledge.
Thanks & regards,
Sugata Bagchi.

hi,
have you checked:
http://help.sap.com/saphelp_nw73/helpdata/en/cc/be413f7c8c4f978b7c755a4bc957d8/frameset.htm
point 10
"If you want the receiver IDoc adapter to use the adapter specific XI information to update the control record of the incoming payload choose Not Mandatory in the Control Record in IDoc XML."
Regards,
Michal Krawczyk

Message determination and Partner function LS (Logical system) for PO

Hi,
I have worked in the past with vendors (VN) as partner roles in a PO, with the message to create an EDI outpout to Partner Type: LI (Vendor), and this works succesfully.
Now, the idea was to use in EDI, a Partner Type: LS (Logical system) as a receiver of EDI messages (message types: ORDERS) for inbound Purchase Orders to the Partner.
So, we have set up a respective message condition, with Partner Function: LS (Logical System), in transaction: MN04 (Create Output-condition records).
A. When we use ME59N and create a PO with ref. from a PR (created from a sales order), the message determination works well, it reads the condition set in MN04 (condition records for messages), and creates a message (with output type for EDI , medium: 6, and partner function LS: Logical system). Message is created and idoc is sent to partner.
B. When we try with ME21N, ME21 and we create the PO with ref. to the same PR, either by entering manually the PR in the document overview of ME21N or by selecting the PR (without entering the PR number), i.e with date, the message is not created in the PO.
Company code is assigned to purchase organization, and so is purchase organization to plant.
Any idea why there is no automatic message determination in the case of the transaction: ME21N?
There is a single message condition that is to be read for both cases (trans: ME59N and ME21N).
Note: If I try ME21N, and enter the output type and partner (=Logical System), manually, I receive a warning message :
VN006 (Partner XXXX does not exist for partner function LS). If I accept this warning message, then message is saved- idoc is sent.
However you can not assign a partner function LS to a vendor, in vendor master data, because of message CZ 327 (Can not use this partner role).
Anyone with similar experience? Thank you for your advice.

Hi,
I well understand that the receiving partner can be a partner: Vendor (LI).
I have seen that working.
However, in the Partner Profiles (trans: WE20), the receiver was created as a Logical System (LS).
We want the partner Logical system (LS) to receive the idoc for purchase order (ORDERS).
After that, I think that the idea is that the LS can generate an idoc for a sales order creation that will then outbound to another partner. I think that this is the concept.
The issue is that I have seen that the POs created with transaction: ME59N, have received from message determination (trans: MN04) the message with partner LS (automatically), and the idoc of the purchase order (ORDERS) have reached the partner LS.
The question is why the message determination fails when creating the PO from trans: ME21N or ME21, with reference to the PR. Message condition is the same and message determination procedure is the same for both cases.
There is no issue with customizing for the LS in trans: WE20
(Port processing agent is Active for LS and ORDERS have the proper processing code for application EF).
I hope I am helping more with this.

Error when trying to receive an encrypted AS/2 message

Hello all,
I'm currently working on an AS/2 implementation (my first BizTalk project) and I'm facing an issue with certificates. I've checked numerous websites, blogs, MSDN and until now, I don't get it working.
Here's the scenario:
From a specific partner, I need to receive an AS/2 encrypted message.
Here's how I test this:
- I have my local computer and a server which both run BizTalk 2013.
- I have generated 1 certificate (DES3 2048 bits) by using OpenSSL.
The certificates are installed as follows:
Sending machine: Local Computer\Other People (My CER file).
Sending machine: Local Computer\Trusted Root Certification Authorities (My CER file) - To make the certificate trusted.
Receiving machine: Current User\Personal Store (My PFX file) - NOTE: Current user is the user under which the In-Process host instance of BizTalk is running.
Receiving machine: Current User\Personal Store (My PFX file) - to make the certificate trusted. - NOTE: Current user is the user under which the In-Process host instance of BizTalk is running.
In IIS, the application pool running the BTSHttpReceive.dll is running under the ApplicationPoolIdentity.
And finally, here's the BizTalk configuration:
(Sending parter):
- Send port -> Certificate: Receiving parner certificate (CER).
- Pary agreement (Sending partner -> Receing partner) -> Validation: "Message should be encrypted is selected" and the encryption algorithm is set to DES3.
(Receiving partner):
- Host (BizTalkServerApplication) -> Certificates: My certificate (PFX).
- Party agreement (Sendingp partner -> Receing partner) -> Validation: "Message should be encrypted is selected" and encryption algorithm is set to DES3.
When I try to send a message from the sending computer to the receiving computer (just a text file with one line) the receiving computer generates two errors in BizTalk Event Viewer:
Error message 1:
The AS2 Decoder encountered an exception during processing. Details of the message and exception are as follows: AS2-From:"AS2-xxx" AS2-To:"AS2-xxx" MessageID:"<xxx_EE47EC3F-A253-48E3-90FB-45849E793E06>" MessageType:
"unknown" Exception:"An error occurred when decrypting an AS2 message."
Error message 2:
A message received by adapter "HTTP" on receive location "xxx" with URI "/BTSHttpReceive.dll" is suspended.
Error details: An output message of the component "Microsoft.BizTalk.EdiInt.PipelineComponents" in receive pipeline "Microsoft.BizTalk.EdiInt.DefaultPipelines.AS2Receive, Microsoft.BizTalk.Edi.EdiIntPipelines, Version=3.0.1.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35" is suspended due to the following error:
An error occurred when decrypting an AS2 message..
The sequence number of the suspended message is 2.
MessageId: {BFE72958-E968-4FF6-B7DA-EB31340D81F6}
InstanceID: {B2B08761-4403-44AE-A788-D487F94CC270}
Here's what I have checked already:
Serial numbers or the certificate as I've seen that this might cause an issue:
Sending computer certificate serial number: ‎00 8a 42 09 ee af c2 29 b1
Receiving computer certificate serial number: ‎00 8a 42 09 ee af c2 29 b1
I hope someone can point me in the right direction because I'm searching for days on this issue.
Kind regards,

Thanks for your response but I must say that I've managed to find the issue. It seems that the decrypting certificate should be registeren as the BizTalk Isolated Host process user account.
Anyway, that solved my issue.
Glad that you've solved your problem by yourself, thanks for sharing your solution. :)

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

RECEIVING PARTNER DESCRIPTION

Similar Messages

Maybe you are looking for